public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Weird fuel behavior
Date: Mon, 19 Jul 2004 02:50:00 -0000	[thread overview]
Message-ID: <l03130303bd20ae491dea@[212.181.162.155]> (raw)
In-Reply-To: <40FAF653.9090602@phy.cmich.edu>

>With the Tcl/Tk interface, I get a warning when trying to load lhs.
>Xconq says that it cannot find the image for 'radar'.

This seems to be a bug in the game module, which lists an empty string as
the image name:

(unit-type radar (image-name "") (char "r")
  (help "looks for units"))
(unit-type artillery (image-name "pz-how") (char "A")
  (help "blows things up at a distance"))

However, the correct image is eventually loaded using the unit type name as
a backup, so the warning is a little premature.

>We shouldn't have to resort to quoting GDL when explaining a game's
>behavior.

Well, one purpose of this list is to teach those who are interested how to
use GDL, which is why I frequently give examples. But more documentation
would also be helpful.

>I see that this table is not described by the help system. I will add it
>once I get back into the utype descriptions as part of the help system
>overhaul.

Good.

Hans


  reply	other threads:[~2004-07-18 23:06 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 [this message]
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
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='l03130303bd20ae491dea@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --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).