From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: slow?
Date: Mon, 12 Jul 2004 08:56:00 -0000 [thread overview]
Message-ID: <l03130303bd17e5b4f168@[212.181.162.155]> (raw)
In-Reply-To: <40F20A95.7090101@phy.cmich.edu>
>Robert Goulding wrote:
>
>> 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).
>
>I would agree that the game graphics are now moving at a creep. Playing
>Win32 Tkconq on my virtual machine was slow to start with, but now cell
>display updates are downright sluggish. It may be a side effect of Hans'
>earlier chckin to fix the unremoved unit images problem that you and
>others reported earlier.
The code now always draws adjacent cells, which is a temporary fix. I
didn't notice much of a slowdown, but it does of course depend on the game
you are playing as well as on the system.
Hans
prev parent reply other threads:[~2004-07-12 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 3:50 slow? Robert Goulding
2004-07-12 6:13 ` slow? Eric McDonald
2004-07-12 8:56 ` Hans Ronne [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='l03130303bd17e5b4f168@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=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).