public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Weird fuel behavior
Date: Tue, 20 Jul 2004 19:50:00 -0000	[thread overview]
Message-ID: <l03130300bd231e9e65a6@[212.181.162.155]> (raw)
In-Reply-To: <200407201539.i6KFdv219401@panix5.panix.com>

>> If you ctrl-click on a unit, it brings up a small closeup (floating window)
>> where you can examine its plans etc. Basically the same information as in
>> the unit info pane.
>
>So you could open these for a few units and keep them open and they'd
>get updated as the game proceeds?  If so, that sounds like the key
>advantage - watching them change, rather than just getting a static
>view of a unit.

That is how it works. Very helful both for debugging and for game design.

>> The only thing that has held me off so far is the poor support for
>> floating windows in tcltk. It took a lot of work to get the research
>> popup window to behave the way it does, and it is still inferior to a
>> real floating window.
>
>Well, I understand the reluctance.  I think maybe the research window
>has been improved since the last time I played a game which has
>research, but I remember quirks (like not bringing it to the front
>when desired or something

This has been fixed now. But it took some work to get it right.

, I don't really remember fully and some of
>them might be related to how research interacts with turns and
>movement, not just the floating-ness of the window as such).
>
>In SDL, I assume we'd get to write our own window code (or use one of
>the many libraries out there which are designed to go on top of SDL).
>I don't know whether that is better or worse than having (possibly
>buggy or quirky) floating windows provided for us.

SDL doesn't support multiple windows at all. So I guess one would have to
implement something like a row of unit info panes in order to examin
several units at once.

Hans



  reply	other threads:[~2004-07-20 19:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17  9:50 Robert Goulding
2004-07-17  9:57 ` Hans Ronne
2004-07-17 14:16   ` Robert Goulding
2004-07-17 20:06     ` Hans Ronne
2004-07-17 20:31       ` Robert Goulding
2004-07-17 21:13         ` Hans Ronne
2004-07-17 21:31           ` Robert Goulding
2004-07-18 13:07             ` Hans Ronne
2004-07-18 20:20               ` Robert Goulding
2004-07-18 22:14                 ` Hans Ronne
2004-07-18 22:16                   ` Eric McDonald
2004-07-19  2:50                     ` Hans Ronne
2004-07-20  8:05                     ` Jim Kingdon
2004-07-20 13:38                       ` Hans Ronne
2004-07-20 19:19                         ` Jim Kingdon
2004-07-20 19:50                           ` Hans Ronne [this message]
2004-07-20 21:36                             ` Eric McDonald
2004-07-20 22:07                               ` Hans Ronne
2004-07-20 23:12                                 ` Eric McDonald
2004-07-21  0:32                                   ` Stan Shebs
2004-07-21  0:47                                     ` Eric McDonald
2004-07-21  1:11                                       ` Hans Ronne
2004-07-21  1:33                                         ` Eric McDonald
2004-07-24 23:19                                           ` Action-Notices list Elijah Meeks
2004-07-26  1:31                                             ` Eric McDonald
2004-07-21  0:55                                   ` Weird fuel behavior Hans Ronne
2004-07-24 20:50                                     ` Eric McDonald
2004-07-20 15:17                       ` Eric McDonald
2004-07-20 15:40                         ` Jim Kingdon
2004-07-19  3:07                   ` Robert Goulding
2004-07-17 12:47 Hans Ronne
2004-07-19  8:07 Robert Goulding
2004-07-19 18:14 ` Hans Ronne

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='l03130300bd231e9e65a6@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --cc=kingdon@panix.com \
    --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).