[aprssig] Public Icon Set (overlay location)

[Lynn W. Deffenbaugh (Mr)]

Or are you proposing they come from the definition, not over-the-air?  
If so (in the defintion), then why constrain to 4 options (2 bit).  Go 
with 9.

Upper Left, Top Center, Upper Right
Left Center Right
Bottom Left, Bottom Center, Bottom Right

And another indicator to say "Overlay" (inside the symbol image) or 
"Outside" (IOMCO*)

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

*IOMCO - Intuitively Obvious to the Most Casual Observer

On 10/8/2013 10:06 AM, Lynn W. Deffenbaugh (Mr) wrote:
> And where do these two bits come from?
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> On 10/8/2013 8:23 AM, Robert Bruninga wrote:
>>
>> One thing to consider is Overlay characters.
>>
>> Originally in APRSdos the overlay characters were drawn over the 
>> symbol itself and those symbols were drawn to have a clear spot in 
>> the center.
>>
>> Then in the Kenwoods, we suggested placing the overlay character in 
>> the upper left corner so that they could appear over any/all symbols.
>>
>> In any new system I suggest 2 bits be allocated to indicate where the 
>> overlay character is drawn.  Upper left, Upper right, center, or 
>> none.  "None" can be used when a client that has defined a separate 
>> symbol for a given overlay combo because it does not then also need 
>> to draw the overlay character.  Though if there is room, it would 
>> help human understanding across platforms if the overlay character 
>> was also obvious on the new special symbol.
>>
>> Bob, WB4APR
>>
>>
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20131008/a2f914a6/attachment.html>