Author: roltman
Subject: Nearest freq: a/p ID bug, and missing a/ports?
Posted: 19 Dec 2014 at 4:09pm
Thinking out of the box here...
I notice some are too big to be displayed on one line anyway, why not use the currently vacant 2nd line to just always say the type?
Albuquerque Approach
(Approach Control)
Genk Radio
(Information)
I'm sure there's reasons for it all being on the first line, but doing above negates all expenses with programming special cases and it'll more or less be future proof.
Just a thought.
<EDIT> Of course I didn't re-read the whole thread so this post could be pointless </EDIT>
Edited by roltman - 14 hours 49 minutes ago at 4:11pm
Subject: Nearest freq: a/p ID bug, and missing a/ports?
Posted: 19 Dec 2014 at 4:09pm
Thinking out of the box here...
I notice some are too big to be displayed on one line anyway, why not use the currently vacant 2nd line to just always say the type?
Albuquerque Approach
(Approach Control)
Genk Radio
(Information)
I'm sure there's reasons for it all being on the first line, but doing above negates all expenses with programming special cases and it'll more or less be future proof.
Just a thought.
<EDIT> Of course I didn't re-read the whole thread so this post could be pointless </EDIT>
Edited by roltman - 14 hours 49 minutes ago at 4:11pm