On Mon, Jul 02, 2007 at 09:49:14AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Forwarded as per Tom's suggestion (originally part of > a long string of emails)
As a summary of the missing bits of the conversation: - Some APRS clients will pop up an incoming message box when a message is received addressed to an object owned by that station. - This behavior was counted on by Bob Bruninga when he advocated setting up "XXX-n" objects for Field Day "blind contacts" on APRS - Xastir doesn't do this. The decode_message function checks only if the message is addressed to our own callsign-ssid or base call sign (no SSID). - Right now, to check an object for ownership, you have to call is_my_object_item with a DataRow pointer, not a call sign. We have a function "is_my_call" that takes a call sign and checks if it's ours, but no similar function to check if a named object is ours. Since objects receiving messages (but not sending or ACKing them) is apparently consistent with the spec, perhaps we should make it work. Especially since not supporting that capability would have made Xastir one of the clients that couldn't have played along with the Field Day plans hashed out on APRSSIG. The original string of emails with Alex was about a slightly different use for this feature, but it's the same deal. You can't send messages to objects that Xastir owns and expect the user to see them. > --- Tom Russo <[EMAIL PROTECTED]> wrote: > > > Date: Mon, 2 Jul 2007 00:09:47 -0600 > > From: Tom Russo <[EMAIL PROTECTED]> > > To: Alex Carver <[EMAIL PROTECTED]> > > Subject: Re: [Xastir] Xastir responding to ?APRSS > > > > On Sun, Jul 01, 2007 at 10:54:30PM -0700, we > > recorded a bogon-computron collision of the > > <[EMAIL PROTECTED]> flavor, containing: > > > Would Xastir show a message directed at an > > > object that it owns? > > > > Look in db.c, the function "decode_message" --- this > > explicitly checks > > the messages "to" against our call sign (with SSID) > > and our base call > > (ignoring SSID), but does not check against any of > > our own objects. > > > > There is no function (that I can see) that provides > > a quick check if > > a call-sign is actually an object owned by > > ourselves, but it shouldn't > > be *that* difficult to write one and use it to > > perform an additional > > check in that routine to make us respond to that > > message. > > > > Thing is, we are not supposed to ACK messages sent > > to our own objects, > > just those sent to our station. (That is something > > that Bob Bruninga > > did comment on when he was advocating using such > > objects and sending messages > > to them during Field Day.) > > > > You might want to take this part of your message > > back to the group for > > discussion. > > > Is there a function that can return currently owned > objects? If not, is there an array or linked list > somewhere that contains the objects in some way (this > I assume exists otherwise Xastir would never remember > its objects). > > > > ____________________________________________________________________________________ > Building a website is a piece of cake. Yahoo! Small Business gives you all > the tools to get online. > http://smallbusiness.yahoo.com/webhosting > _______________________________________________ > Xastir mailing list > Xastir@xastir.org > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir -- 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 _______________________________________________ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir