[Xastir] problem messaging

[Curt Mills]

On Fri, 20 Sep 2002, J. Lance Cotton wrote:

> I've notice that this "return path guessing" fouls up a little bit with
> INET received messages that use the Q-construct. I usually get a guessed
> path of something like:   N5JXS,qAS
> Where the message might have come from N5JXS directly over INET.

If you're talking to a station who's directly on the NET, then the
path doesn't matter at all.

As the code currently stands, the path gets associated with your
outgoing packet when you hit the "Send Now!" button.  That packet
then sits in the outgoing queue with that path until it gets ack'ed
or times out.  You can change the path for each line you type.

The Q-construct was invented after the path guessing stuff was
written.  When it started to be used, Xastir trashed all packets
containing it because it wasn't a valid callsign.  A quick hack to
that part of the code allowed it through, but no other work has been
done to accomodate this construct.

Yet another thing to get to.

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_ at tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"