[aprssig] Object Timestamps and 111111

Bob Bruninga bruninga at usna.edu
Sun Dec 12 23:25:24 CST 2010


Well, apparently I went by someone elses info that UIview would ignore the 000000z object.  Sorry.  Maybe it was some other popular client.  But in any case, I remembered it was a client that could not be upgraded and so maybe that's why I remembered it as UIview.

I wonder if it was a kenwood instead?
Thanks for checking and filling us in on UIview's broader acceptance of that field.  I doubt I could ever find the original thread that drove this...


---- Original message ----
>Date: Sun, 12 Dec 2010 14:05:18 -0800
>From: aprssig-bounces at tapr.org (on behalf of "Keith VE7GDH" <ve7gdh at rac.ca>)
>Subject: Re: [aprssig] Object Timestamps and 111111  
>To: "TAPR APRS Mailing List" <aprssig at tapr.org>
>Bob WB4APR wrote...
>> Its a crutch for UI-View that cannot be fixed. We needed a
>> NULL value for the date/time stamp for objects that are either
>> permanent or the source has no clock.  We tried 000000z, but
>> UI-View then completely ignores the object. Not good.
>It's funny how these myths get started. UI-View does NOT ignore
>an object if the time is "      z" (6 spaces) or "       " (7 spaces) or
>"000000Z" or "111111z" or "111111h". They work just fine.
>> So, the only thing we can do is come up with another value.
>> We chose 111111z as an easy to recognize null value.
>As mentioned above, 111111z works just fine in UI-View.
>If you have an example of an object that UI-View ignores, I would be
>happy to look at it and test it for you in UI-View 2.03.
>73 es cul - Keith VE7GDH
>"I may be lost, but I know exactly where I am!"
>aprssig mailing list
>aprssig at tapr.org

More information about the aprssig mailing list