The beacon list shows new for worked callsign with a prefix. E.g. it displays in green instead of no highlighting. So it misleads and you can't see who you already worked!
Example 1: I7/KJ4YBS
Example 2: SV8/SV1AAW
8 comments
Like
8 Comments
Commenting on this post isn't available anymore. Contact the site owner for more info.
I'm now on 11.0.7 and I notice that worked stations with prefixes are still marked as new (in green). Example: I7/KJ4YBS.
He is not just marked as new -- also, *** his location is wrong ***! The mouseover shows him as in the United States!
However his Grid is listed. So maybe at least use that? If the grid is in Italy, then his country is NOT the US! And it also proved that I worked him before! So it should remove the green highlight!
Another idea, until longer callsigns than 7 characters, you could stuff the prefix into a different part of the message, or if the callsign is under seven characters, add a special character like /, even if the rest of the prefix is truncated.
This features was not developed yet and still in the to-do list. no need to report the same thing again. the release notes of V11 did not state it was developed/fixed
Can't. Beacons only carries 7 characters long callsign. This may change when I use ax25 for an SL2 beacons where I'll also include locator ans some more data
In the meantime, maybe you could include the prefix in the message payload, and parse it.E.g.,From station: SV1AAWMessage Payload: <P>SV8</P>This broadcast is from John SV8/SV1AAW.
Scope update:
It's not just callsigns with a prefix. The issue also affect callsigns with a a suffix!
Spotted in VarAC V11.2.0.
Example:
I already worked station FR4KF/ADRASEC 974 - tag: <FC:FR4KF/ADRASEC 974>.
I'm now on 11.0.7 and I notice that worked stations with prefixes are still marked as new (in green). Example: I7/KJ4YBS.
He is not just marked as new -- also, *** his location is wrong ***! The mouseover shows him as in the United States!
However his Grid is listed. So maybe at least use that? If the grid is in Italy, then his country is NOT the US! And it also proved that I worked him before! So it should remove the green highlight!
Another idea, until longer callsigns than 7 characters, you could stuff the prefix into a different part of the message, or if the callsign is under seven characters, add a special character like /, even if the rest of the prefix is truncated.
Can't. Beacons only carries 7 characters long callsign. This may change when I use ax25 for an SL2 beacons where I'll also include locator ans some more data
Confirmed. will be added to the to-do bug list