public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: New Windows Installer and Source Tarballs
Date: Mon, 11 Oct 2004 06:26:00 -0000	[thread overview]
Message-ID: <1097463166.4188.3877.camel@localhost> (raw)
In-Reply-To: <20041011014555.11750.qmail@web13122.mail.yahoo.com>

On Sun, 2004-10-10 at 18:45, Elijah Meeks wrote:
> I don't have the .xcq in front of me, but I'll check
> it as soon as I can.  The two tables are:
> 
> (table see-mistake-chance
>    (lrsensors ship-types 10000)
>    (damlrsensors ship-types 10000)
> 
> )
> 
> (table looks-like
>    (ship-types fedmarker 10000)
> )

One possible issue I see is that (to my knowledge) there is no mechanism
by which the view code could determine whether the unit you see is a
"ship-types" unit or a "fedmarker" unit.  You would need a way for the
views of other units to override the views of "lrsensors" and
"damlrsensors" units when you get close enough for more accurate
short-range sensors to take over.

This would not be easy to fix, as you would need some mechanism to
determine which unit view would take priority.  This would have to be
added as either a unit property (u_view_priority) or a table
(uu_view_priority), depending on how much detail you need.

---
Lincoln Peters
<sampln@sbcglobal.net>

Too much is just enough.
		-- Mark Twain, on whiskey

      parent reply	other threads:[~2004-10-11  2:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 22:52 Eric McDonald
2004-10-10 22:56 ` Elijah Meeks
2004-10-10 22:59   ` Lincoln Peters
2004-10-11  1:45   ` Eric McDonald
2004-10-11  2:06     ` Elijah Meeks
2004-10-11  2:49       ` Eric McDonald
2004-10-11  6:26       ` Lincoln Peters [this message]

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=1097463166.4188.3877.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=elijahmeeks@yahoo.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).