From: "Robert Goulding" <Goulding.2@nd.edu>
To: <xconq7@sources.redhat.com>
Subject: slow?
Date: Mon, 12 Jul 2004 03:50:00 -0000 [thread overview]
Message-ID: <009601c467c0$248defc0$feb3fea9@blackbox> (raw)
On recompiling from CVS, the display bug under WinTCL seems to be gone, in
the same game I was playing in which I first noticed it. But my subjective
impression is that the game is running *much* more slowly, especially, I
think, when units are sent to resupply (is this a side effect of the new
resupply code?). I have no idea how to read the debug information, but when
I set DD, there were many lines of the sort 'Did nothing 1000 times' (which
may be normal); and with DG set the display seemed to be hovering for a
*long* time around the same area (which is also the impression I get when
playing).
Robert.
next reply other threads:[~2004-07-12 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 3:50 Robert Goulding [this message]
2004-07-12 6:13 ` slow? Eric McDonald
2004-07-12 8:56 ` slow? 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='009601c467c0$248defc0$feb3fea9@blackbox' \
--to=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).