public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: mcdonald@phy.cmich.edu
Cc: xconq7@sources.redhat.com
Subject: Re: Another Possible Solution to the Occupants Display Problem
Date: Mon, 06 Sep 2004 20:49:00 -0000	[thread overview]
Message-ID: <200409061942.i86Jgq712540@panix5.panix.com> (raw)
In-Reply-To: <413CB191.4060205@phy.cmich.edu> (message from Eric McDonald on Mon, 06 Sep 2004 12:50:57 -0600)

> "Occs" is a button that brings up a popup containing images of the
> occupants.

Instead of "Occs" or "OV", I think I'd go with an icon (if someone can
design one which makes sense and fits in 16x8 or so).  Or maybe just
"...".  That fits in almost any size box and seems to be kind of
logical for what the button does (and indicates).  Or maybe just draw
the transport full-size in the "unit in a white box meaning occupants"
which the tcltk interface now uses at 16x16 (hmm, I guess that only
works if the popup is a mouseover, because click means to act on that
unit).

> For 11x11 (8x8), clicking anywhere in the transport should probably
> bring up the occupant view popup.

Yes.  Likewise at any magnification for clicking on occupants which
are displayed in the transport (in the 1-2 occupant case).

But it seems odd for click to sometimes mean act on the unit and
sometimes mean bring up the popup.  I'm thinking more that the popup
should be a mouseover (although I don't know about things like nested
popups in that context).

> the transport's name, location, and similarly-sized image should be
> near the top of the popup

Also ACPs, materials and plans (hit points optionally, although there
is already a damage bar for that).  As long as we are bringing up a
popup, might as well make it possible to avoid having to glance over
to a separate unit details pane.

I'm not as sure about location - it seems like the fact that you get
to the popup from the map maybe means location is reduant.  It seems
kind of inelegant to be using a bunch of text if there is some way to
provide the information visually in a contextual way.

Anyway, if the popup has this kind of information, it would be useful
to be able to bring up this popup by clicking on the transport itself
(or a unit with no occupants).

> Thoughts?

I don't remember what the other choices du jour were, but this one
seems promising.  Or some variant thereof...

I think the main alternative which is springing to mind is being able
to magnify the map more than you can now (with probably a key or
something which takes you immediately to the maximum zoom which is
needed to see the selected unit and its occupants, or something).

  reply	other threads:[~2004-09-06 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 19:42 Eric McDonald
2004-09-06 20:49 ` Jim Kingdon [this message]
2004-09-06 22:09   ` Eric McDonald
2004-09-07 17:03     ` Jim Kingdon
2004-09-08  1:29       ` 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=200409061942.i86Jgq712540@panix5.panix.com \
    --to=kingdon@panix.com \
    --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).