public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Research of Advances and SDL UI Improvements
Date: Wed, 08 Sep 2004 03:54:00 -0000	[thread overview]
Message-ID: <413E821F.3070404@phy.cmich.edu> (raw)
In-Reply-To: <1094613359.4338.58434.camel@localhost>

Lincoln Peters wrote:

> In that case, I'll comment out this part of the code until these tables
> are implemented.

I'll comment out the [ir]relevant documentation.

During my work on implementing unit research and side research support 
in the SDL interface, I discovered that unit research appears to be 
broken/unsupported in the kernel. Only side research appears to work. 
So, there seems to be a lot of little things broken regarding advances.

I just need to do a couple more tweaks to the SDL interface and then I 
think I'll be ready to provide a new prerelease for download. Quite a 
few bugfixes, and some improvements. Here is a sampling:
(1) Prompts for things like saving the game, choosing a build location, 
etc... now appear in the mouseover panel so that there is some indicator 
when the interface is in a "mode" and expecting an user response. (Note 
that the game does not actually save yet, but it pretends to, so that 
one can quit without loss of face (resignation).)
(2) Prefix args are accepted and apply to unit action buttons 
(construct, develop, change type, research) as is relevant 
(construction), as well as the keyboard commands. The mouseover panel 
displays the number of times a construction task will try to execute 
(from doctrine or prefix arg).
(3) If a prefix arg is not specified then the construction buttons 
indicate (via the mouseover panel) the construction run length provided 
by the doctrine (or 1, failing that).
(4) Unit research is supported, but presently useless (see above).
(5) Side research is supported.
(6) Clicking on a cell in which to construct now works correctly. 
Previously, the coords of the target cell were not being picked up.
(7) The title of the window is now of the form, "Xconq - <Game Title> - 
<Side Name> - <Turn Number>" and the taskbar caption is of the form, 
"Xconq - <Game Title>".
Etc, etc....

Hopefully, I'll make it available tomorrow or Thursday evening. After 
that, I will try to finish filling out the other possible unit action 
buttons: delay, skip, sleep, join formation, leave formation, gather 
materials, take needed materials from unit in range, resume stagnant 
build on unit in range, repair unit in range, give needed materials to 
unit in range, help build on unit in range, etc.... In survey mode, 
other possible buttons would include: cancel plan, wake, etc....

Eric

  reply	other threads:[~2004-09-08  3:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08  1:51 Problem compiling new version of ai_plan_research Lincoln Peters
2004-09-08  3:39 ` Eric McDonald
2004-09-08  5:20   ` Lincoln Peters
2004-09-08  3:49     ` Eric McDonald
2004-09-08  3:53       ` Lincoln Peters
2004-09-08  3:54         ` Eric McDonald [this message]
2004-09-08  3:47 ` Politics Elijah Meeks
2004-09-08  8:27   ` Politics Lincoln Peters
2004-09-08 19:30     ` Politics Eric McDonald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=413E821F.3070404@phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).