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: time.g weirdness
Date: Wed, 11 Aug 2004 16:34:00 -0000	[thread overview]
Message-ID: <l03130300bd3ff7809353@[212.181.162.155]> (raw)
In-Reply-To: <200408111555.i7BFt9e09071@panix5.panix.com>

>It also might be nice if the online help said something a bit more
>than just:
>
>  Needs MP to enter terrain: 99 by default, 1 into sea, shallows, 0 into
>  river.
>  Needs MP to traverse terrain: -1 by default, 2 across river.
>
>although I'm not really sure how to express this best.  I guess the
>"99 by default" could be turned into "cannot enter other terrain" (if
>the help code can figure out that 99 is never possible).  Something
>similar for the "-1 by default".

Heh, that makes me recall the long and at the end almost metaphyscial
discussion I had with Peter Garrone last year about the meaning of the
number "99" :-).

>Although I suppose the real problem here is that the online help
>doesn't know about the user interface, so it can't just say "to travel
>along a river, click ....".  Maybe the user interface could have some
>kind of mouseover (I could threaten to make it a tooltip for Xconq
>Office) when you are on a unit which has a border slide possible.  Or
>something along these lines...
>
>Of course, all this is predicated on making border slides work from
>the user interface in the first place.

Right. I'm looking into this. Even more important, however, is to fix the
"map the unknown by clicking in it" exploit, which sneaked back in when we
removed Peter's pathfinding.

Hans


  reply	other threads:[~2004-08-11 16:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 17:51 Robert Goulding
2004-08-10 18:11 ` Hans Ronne
2004-08-11  1:23 ` Hans Ronne
2004-08-11 16:34   ` Jim Kingdon
2004-08-11 16:34     ` Hans Ronne [this message]
2004-08-11 16:47       ` Eric McDonald
2004-08-11 17:09         ` Hans Ronne
2004-08-12  4:03           ` Eric McDonald
2004-08-12 11:16             ` Hans Ronne
2004-08-11 16:41     ` Eric McDonald
2004-08-12  8:42       ` Jim Kingdon
2004-08-12  8:56         ` Hans Ronne
2004-08-12 15:42           ` Jim Kingdon
2004-08-12 16:58             ` Eric McDonald
2004-08-12 17:35               ` Hans Ronne
2004-08-12 16:55         ` Eric McDonald
2004-08-12 15:39 ` Hans Ronne
2004-08-12 16:53   ` Jim Kingdon
2004-08-12 16:59     ` Hans Ronne
2004-08-12 17:08     ` Eric McDonald
2004-08-12 17:19       ` Hans Ronne
2004-08-12 17:24         ` Eric McDonald
2004-08-12 18:15           ` Hans Ronne
2004-08-13 23:46             ` Eric McDonald
2004-08-14  3:50             ` Wrecked-Type Doesn't Apply to Detonating Units Elijah Meeks
2004-08-14  9:19               ` Eric McDonald
2004-08-14 15:36                 ` Hans Ronne
2004-08-14 16:00                   ` Eric McDonald
2004-08-14 17:42                     ` Eric McDonald
2004-08-16  0:27                 ` Elijah Meeks
2004-08-16 18:24                   ` Eric McDonald
2004-08-16 21:34                     ` Elijah Meeks
2004-08-17  0:50                       ` 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='l03130300bd3ff7809353@[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).