[Xastir] interface.c

[Tom Russo]

On Tue, Sep 19, 2006 at 09:05:34PM -0600, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> On Tue, Sep 19, 2006 at 07:34:34PM -0700, we recorded a bogon-computron collision of the <mike_fenske at telus.net> flavor, containing:
> > Just updated to today's CVS and I noticed some odd behaviour that wasn't
> > there before. Here's a capture of the "view incoming data" window shortly
> > after starting Xastir:
> > 
> > 0:TX -> VE7MKF-1>APX183,WIDE2-2:=/5^%o/Ko8x{5Chttp://www3.telus.net/ve7mkf
> > 0:TNC-> >APX183,WIDE2-2:=/5^%o/Ko8x{5Chttp://www3.telus.net/ve7mkf
> > 0:TNC-> >APX183,VE7IPB-10*,WIDE2-1:=/5^%o/Ko8x{5Chttp://www3.telus.net/ve7mkf
> > 0:TNC-> >APX183,OTTER*,WIDE2-1:=/5^%o/Ko8x{5Chttp://www3.telus.net/ve7mkf
> 
> Are you running an AX.25 port?

My claim that I was seeing this on my home machine was false --- I 
misunderstood what you were pointing out here.

The code in data_out_ax25 tries to parse the MYCALL line that 
output_my_aprs_data produces, and it was getting confused by the fact that
there was a carriage return at the beginning of the line --- it is looking
for a carriage return as the delimiter at the end of the line, and assuming
that whatever comes immediately before it is the callsign.

Naturally, when I stuck a \r at the beginning of the line, that meant that 
AX25 ports started thinking that there *WAS* no callsign.

I just checked in a quick fix that refrains from putting in the \r if the
port is an AX.25 port, but puts it in if it's a regular TNC.

The right way to fix this would be to change data_out_ax25 so it isn't 
confused by the leading \r.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick