From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Bugs in SDL interface
Date: Sat, 28 Aug 2004 05:08:00 -0000 [thread overview]
Message-ID: <41300FA4.5080900@phy.cmich.edu> (raw)
In-Reply-To: <1093156811.2792.5375.camel@localhost>
Lincoln Peters wrote:
> 4. When I change the zoom, the main panel shifts to display a different
> part of the map. And strangely enough, it seems to shift to the same
> spot every time, although a different spot for each level of
> magnification. I think we all agree that it should remain centered on
> the same point when the zoom changes.
I have fixed this in my sources.
> 5. In the Standard game, roads do not appear at maximum zoom. They seem
> to appear properly at all other zooms (except the lowest, where they'd
> be an eyesore). I haven't tried it with other games.
I was able to reproduce this. I am not ready to fix it yet.
> 6. There needs to be an easy way to tell which units have remaining
> ACP's and are not in Reserve or Asleep *without* clicking on them,
> unless the unit focus will automatically switch to the next such unit
> when the currently-selected unit cannot perform additional actions this
> turn. Otherwise, making sure that all units have acted in a given turn
> is a real pain.
This was a remarkably simple fix. One line, in fact. The SDL interface
in my sources now automatically selects the next unit to act, just as in
the Tcl/Tk interface.
> 8. There should be some kind of feedback for combat situations. Not
> necessarily explosions (although that might be useful, if done
> correctly), but some way to tell what happened without having to run
> Xconq from an XTerm and flip between the two windows up to 20 times per
> minute. The best way I can think of to do this is by using a status bar
> for messages such as "Your * can never do this!", and a collapsible log
> panel for messages such as "You completed your *".
I think this feedback should go in a panel along the bottom of the
screen. I have been somewhat tempted to move the panel with the unit
info off to the right side of the screen to help square up the aspect
ratio (as in TOAW), and make room for notices along the bottom. Still
not sure yet, especially since it looks like a line or two could be
squeezed out of the unit info panel on the bottom, and, depending on how
text is rendered, there could be severe truncation of the unit info
strings, if they were put on a narrower panel on the right side of the
screen.
Eric
prev parent reply other threads:[~2004-08-28 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 6:39 Lincoln Peters
2004-08-22 13:13 ` Hans Ronne
2004-08-23 2:16 ` Lincoln Peters
2004-08-23 4:13 ` Jim Kingdon
2004-08-23 16:41 ` Eric McDonald
2004-08-27 4:36 ` Eric McDonald
2004-08-28 5:08 ` Eric McDonald [this message]
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=41300FA4.5080900@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=sampln@sbcglobal.net \
--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).