[Xastir] Re: [Xastir-dev] Desired object/item operation?

[Curt, WE7U]

On Fri, 7 May 2004, Curt, WE7U wrote:

> While working on that I noticed some inconsistent operation.  It has
> to do with creating objects/items, moving them around, killing them,
> and then creating new objects/items with the same names.
>
> If you do that while Xastir is running continuously, you get
> tracklines from the old killed objects to the new.  You'll see all
> positions of both.
>
> If you do that and then kill/restart Xastir, causing it to load the
> object.log file on startup that way, you only get tracks for the
> "new" objects/items.  The tracks do not go back to the old positions
> before the initial kill.
>
> For SAR I'd like to have a persistent display across restarts.
> Right now the displays are different across a restart.
>
> What is the desired operation here?

Thinking about it three more seconds or so, the object.log file
holds info about objects forever.  It wouldn't make sense to
connect-the-dots to very old objects.  In a search situation, I'd
forever be bringing up the Station Info dialog and clearing the
track for each object the first time I instantiated it, 'cuz it
would connect-the-dots back to a previous mission where I used the
same identifier.

I think that we should ignore any lines with a '#' symbol as the
first character when reading in the object.log file.

Should we also flush all records of a killed object from the running
copy of Xastir, once it has completed the transmissions for the
killed object, or should we connect-the-dots back to the old
object's positions?

--
Curt, WE7U			    archer at eskimo dot com
Arlington, WA, USA		http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"