From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com
Subject: Re: Three thoughts
Date: Fri, 20 Aug 2004 18:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0408201212300.14897-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0408201105280.6658-100000@diamond.ansuz.sooke.bc.ca>
Hi Matthew, long time, no see,
On Fri, 20 Aug 2004 mskala@ansuz.sooke.bc.ca wrote:
> * If firing at specific units were to be a big part of some game, then it
> would be nice if it were easier to designate specific units when there are
> many of them, or nested occupant/transports, in a cell. As it is, even at
> the deepest level of zoom it's quite difficult to click precisely on one
> unit if there are a lot of them in the cell. One way to deal with this
> might be for an interface to be able to give me a dialog box with a list
> of units in the cell.
I think that Elijah may have also mentioned this last year, and I
completely agree. Although I really don't want to do much Tcl/Tk
hacking, this is something that I have been contemplating adding,
depending on whether I let units carry armor (and weapons,
once the necessary 'hit-chance' and 'damage' modifier tables are
in place). Probably such a window could be brought up with the "i"
key, since I think that is supposed to go to the next occ, IIRC.
> myself. Why can't we have scroll bars like everybody else?
Unless I am dreaming, I think the Tcl/Tk interface may have had
scrollbars at some point, or, at least, I thought they were
commented out in the Tcl code. I think Hans did improve the
keyboard navigation in this regard a while back ago. Something
about using the arrow keys or the numeric keypad, IIRC. You might
want to see if you can dig up that mail; it might make your map
navigation a little more pleasant.
Eric
next prev parent reply other threads:[~2004-08-20 16:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 16:22 mskala
2004-08-20 18:34 ` Eric McDonald [this message]
2004-08-20 21:17 ` Andreas Bringedal
2004-08-20 21:28 ` Eric McDonald
2004-08-20 23:57 ` Andreas Bringedal
2004-08-21 1:21 ` Eric McDonald
2004-08-21 4:35 ` Jim Kingdon
2004-08-21 20:38 ` Jim Kingdon
2004-08-20 22:03 ` Elijah Meeks
2004-08-20 23:27 ` Eric McDonald
2004-08-21 1:17 ` mskala
2004-08-21 2:31 ` Eric McDonald
2004-08-21 4:33 ` mskala
2004-08-22 3:09 ` Hans Ronne
2004-08-22 6:38 ` Item Units Elijah Meeks
2004-08-22 9:37 ` Eric McDonald
2004-08-24 1:43 ` Lincoln Peters
2004-08-24 2:38 ` Eric McDonald
2004-08-24 2:51 ` Lincoln Peters
2004-08-24 3:32 ` Eric McDonald
2004-08-22 14:00 ` Three thoughts mskala
2004-08-22 18:56 ` Hans Ronne
2004-08-22 19:16 ` Lincoln Peters
2004-08-23 4:31 ` Jim Kingdon
2004-08-23 13:04 ` Elijah Meeks
2004-08-24 18:07 ` Eric McDonald
2004-08-24 20:59 ` Elijah Meeks
2004-08-25 0:54 ` Unit-Image Bug Elijah Meeks
2004-08-25 4:58 ` Eric McDonald
2004-08-23 16:48 ` Three thoughts Eric McDonald
2004-08-24 0:55 ` Lincoln Peters
2004-08-24 2:09 ` Eric McDonald
2004-08-24 3:02 ` Lincoln Peters
2004-08-24 18:12 ` Eric McDonald
2004-08-25 5:34 ` Jim Kingdon
2004-08-25 17:16 ` Lincoln Peters
2004-08-25 22:09 ` Jim Kingdon
2004-08-26 2:15 ` Eric McDonald
2004-08-26 6:17 ` Jim Kingdon
2004-08-26 19:12 ` Eric McDonald
2004-08-26 22:08 ` CXP??? Elijah Meeks
2004-08-27 1:50 ` CXP??? Lincoln Peters
2004-08-27 5:10 ` CXP??? 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=Pine.LNX.4.44.0408201212300.14897-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--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).