From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Three thoughts
Date: Tue, 24 Aug 2004 18:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0408241402310.15962-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1093315933.2792.30478.camel@localhost>
On Mon, 23 Aug 2004, Lincoln Peters wrote:
> > Well, I never suggested that other get smaller....
> > Does the MacOS X icon bar have that property?
>
> No, but I imagine that if the size of the cell doesn't change, you'd
> have to shrink the other units to accommodate the enlarged unit image
> unless you were willing to obscure units by placing them underneath the
> enlarged unit image (which it looks like was what you have in mind).
Right.
> I noticed that the SDL interface blows up the selected unit to fill the
> entire cell even if other units occupy the cell. I find it to be rather
> awkward,
As do I. I think a more traditional selection rectangle might be
desirable. If one wants to see a full-sized "portrait" of the
selected unit, it can be provided in the unit information panel.
> I de-select the current unit first. And sometimes it looks weird when
> several tiny unit images appear underneath a big unit image.
Agreed. At first I thought I was witnessing a bug, until I
realized what was going on.
> I'm not sure which solution would work better. It might be necessary to
> implement both solutions and see which holds up better in practice.
That might be not be a bad idea. But, I am not going to volunteer
to write both solutions.
> http://homepage.mac.com/lmpeters/cell-closeup2.png
Interesting....
Eric
next prev parent reply other threads:[~2004-08-24 18:07 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
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 [this message]
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.0408241402310.15962-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--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).