Commented-out lines: Seems to be a common complaint of yours these
days. Those of us who aren't as accomplished with Git, not using it
everyday, tend to keep possibly-useful code around in this form. Feel
free to get rid of such lines, at the expense of making it harder for
some of us to look up
On Thu, Jan 20, 2022 at 02:07:41PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> OK, I'll modify the xastir_udp_client documentation to note that injecting
> objects or items into Xastir using the same callsign/SSID as Xastir's will
> cause Xastir to own the object
Thanks!
On Thu, Jan 20, 2022 at 1:34 PM Tom Russo wrote:
>
> On Thu, Jan 20, 2022 at 02:07:41PM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > OK, I'll modify the xastir_udp_client documentation to note that injecting
> > objects or items into Xastir using the
Resurrecting an ancient thread, because Dj opened an issue on GitHub about it
this week, and I tracked down what is happening here. I'm following up to
the original thread to clear up the misunderstanding and get the answer into
the mailing list archive where it could presumably be found in web
On Thu, Jan 20, 2022 at 11:13:52AM -0800, we recorded a bogon-computron
collision of the flavor, containing:
> Commented-out lines: Seems to be a common complaint of yours these
> days.
As someone who's day job involves maintaining an enormous legacy software
package written by some dozen
It's fuzzy in my memory now, but I believe there may be a side-effect
in Xastir as well (which can be taken advantage of in some cases)
where if the call and SSID are the same as the Xastir instance when
injecting packets in via xastir_udp_client, Xastir can take up
re-transmitting those packets
The code is pretty hard to read and is peppered with blocks of commented-out
code that have been that way since 2005. There used to be some attempt to
treat the injected stuff as third-party only if its callsign was different
from Xastir's, but all that is commented out and stuff injected by
Thinking about that another few seconds, the "Those of us who aren't
as accomplished with Git" bit probably means just myself, as we have
only three developers at present.
On Thu, Jan 20, 2022 at 11:13 AM Curt Mills wrote:
>
> Commented-out lines: Seems to be a common complaint of yours these
>
On Thu, Jan 20, 2022 at 1:01 PM Curt Mills wrote:
>
> Where it can be and advantage is if you're trying to inject
> objects/items into Xastir from some other interface, using
> xastir_udp_client to do this injection.
>
That works and I have made use of it during bike events to translate SPOT
Yes, that description of how they get adopted fits my fuzzy
recollection of same. Perhaps others who have used that side-effect
feature can comment.
It'd be good to add a blurb to the man-page about the possibility, so
people don't get confused when things work differently than they
expect.
On
I have not played with Xastir for some time, but yes that side-effect did
exist as I remember using it. I would also agree it occurred only when
using the same callsign and ssid as the Xastir instance.
Brett KQ9N
On Thu, Jan 20, 2022 at 1:33 PM Curt Mills wrote:
> Yes, that description of how
OK, I'll modify the xastir_udp_client documentation to note that injecting
objects or items into Xastir using the same callsign/SSID as Xastir's will
cause Xastir to own the object and retransmit it in the same way that it does
objects created via its interface.
On Thu, Jan 20, 2022 at 01:49:09PM
12 matches
Mail list logo
