public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: "Robert Goulding" <Goulding.2@nd.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Slowness in updating (especially sea) units in standard game (WinTCL)
Date: Sun, 11 Jul 2004 09:49:00 -0000	[thread overview]
Message-ID: <l03130303bd16b60cd3f5@[212.181.162.155]> (raw)
In-Reply-To: <002c01c466fd$e7a3d790$feb3fea9@blackbox>

>Latest CVS of WinTCL - I've just noticed this for the first time playing
>tonight.  As the subject line says, I'm repeatedly finding in playing the
>standard game that icons of sea units are left where there are no longer any
>units, to disappear later in the turn (and ISTR that this same thing
>happens more rarely with aircraft).  It occurs especially with enemy craft,
>but also with my own (I just moved my battleship into a city for refuelling,
>and had 2 icons of it on the map, one in its original location, the other in
>the city).  Several times I've been surrounded by enemy craft, hit 'a' to
>attack, at which point the display seems to update and I no longer have
>*anything* to attack.  As I say, this was not happening yesterday....
>
>Robert.

We are aware of the bug. It is a very strange bug in that it somehow
involves the unit view code, but appears also in see-all games where this
code is not used for drawing.

As Eric mentioned, he doesn't see it under Linux for PC, but I do under
Linux for the Mac. OTOH, I don't see it under MacOS, with either the tcltk
or native Xconq version. We therefore thought that this bug was limited to
Linux for the Mac, but if it also happens in the Windows app it is of
course worse.

Is anybody else seeing it on Linux systems? And is anybody not seeing it
under Windows?

It is not that obvious if you are not aware of the problem, so it can be
easy to miss. Best way to detetct it is in games that start with a fight
like the Korean War or Roman Civil War.

Hans

P.S. The above questions are directed only to those of you who build your
own apps from the CVS sources. The bug appeared on July 8, so it is not
present in any of the recently released binaries.


  parent reply	other threads:[~2004-07-11  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-11  4:25 Robert Goulding
2004-07-11  5:57 ` Eric McDonald
2004-07-11  9:49 ` Hans Ronne [this message]
2004-07-11 10:23   ` Martin Fehlhaber
2004-07-11 12:16     ` Hans Ronne
2004-07-11 15:16   ` Tom Low-Shang
2004-07-11 14:31 ` Hans Ronne

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='l03130303bd16b60cd3f5@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --cc=Goulding.2@nd.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).