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: Fri, 27 Aug 2004 04:36:00 -0000 [thread overview]
Message-ID: <412EB17B.20501@phy.cmich.edu> (raw)
In-Reply-To: <1093156811.2792.5375.camel@localhost>
Lincoln Peters wrote:
> 2. Units that can be developed but have not yet been developed do not
> appear in the list of units that can be built. This makes it impossible
> to develop those units. (I think that a similar bug existed in the
> TclTk interface in 7.4.1 but was fixed in CVS a long time ago.)
I have now changed my sources so that the build buttons either say
"Develop and then Build" or "Build" depending on which is the case. I
tested with 'bolodd3.g', and everything seemed to work as expected.
> 3. The information panel at the bottom of the screen is not updated
> after a mouse click, although it updates properly as soon as I move the
> mouse or some other action takes place. Perhaps the information is
> being refreshed *before* the task is executed?
As with item 1, I could not reproduce this.
> 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 am looking into this and the other issues you raised, plus a few of my
own.
Eric
next prev parent reply other threads:[~2004-08-27 3:59 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 [this message]
2004-08-28 5:08 ` 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=412EB17B.20501@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).