From: Hans Ronne <hronne@comhem.se>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: xconq7@sources.redhat.com
Subject: Re: Reduced Visibility Table?
Date: Tue, 02 Dec 2003 00:58:00 -0000 [thread overview]
Message-ID: <l03130303bbf190c22ddf@[212.181.162.155]> (raw)
In-Reply-To: <1070325128.378.40.camel@odysseus>
>> A related problem is posed by the user area layer that is used by the
>> advanced unit code. You may find that you are unable to use a certain cell
>> because another advanced unit is using it, even though the latter unit is
>> invisible to you.
>
>You might not be able to see the unit that is using the cell, but
>shouldn't you be able to see that the cell is used and act accordingly?
>There would have to be *something* tangible there in order for the other
>unit to use the cell.
That was exactly my point. In the tcltk interface, it is only your
inability to pick a certain cell that tells you somebody else is using it.
In the mac interface, the small map in the advanced unit popup (similar to
the city map in civilization) has a colored square on cells that are used
by enemy units.
Hans
next prev parent reply other threads:[~2003-12-02 0:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 22:35 Elijah Meeks
2003-12-01 23:18 ` Hans Ronne
2003-12-02 1:09 ` Elijah Meeks
2003-12-02 4:02 ` Hans Ronne
2003-12-01 23:23 ` Bruno Boettcher
2003-12-01 23:27 ` Lincoln Peters
2003-12-01 23:43 ` Stan Shebs
2003-12-02 0:30 ` Hans Ronne
2003-12-02 0:54 ` Lincoln Peters
2003-12-02 0:58 ` Hans Ronne [this message]
2003-12-02 4:46 ` Eric McDonald
2003-12-02 4:04 ` Eric McDonald
2003-12-02 4:16 ` Eric McDonald
2003-12-02 20:56 ` Hans Ronne
2003-12-03 2:41 ` Eric McDonald
2003-12-03 3:04 ` Lincoln Peters
2003-12-03 21:13 ` Eric McDonald
2003-12-01 23:32 ` Hans Ronne
2003-12-02 15:04 ` Bruno Boettcher
2003-12-02 19:57 ` Emmanuel Fritsch
2003-12-03 2:12 ` Hans Ronne
2003-12-03 2:22 ` 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='l03130303bbf190c22ddf@[212.181.162.155]' \
--to=hronne@comhem.se \
--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).