It seems to me that I used to see the range and azimuth if I moused over a call sign and now I don't. I didn't see anything in the release notes so it is either my memory fault or a setting I can't find. Not a big deal but I found it useful for NA stations that don't show a state or provence. Windows 10, JTAlert 2.2.8, WSJT-X 2.2.2, HRD5 for logging. Sorry for the edit. John KA5BJC
It
seems to me that I used to see the range and azimuth if I moused
over a call sign and now I don't. I didn't see anything in the
release notes so it is either my memory fault or a setting I can't
find. Not a big deal but I found it useful for NA stations that
don't show a state or provence.
Windows 10, JTAlert 2.2.8, WSJT-X 2.2.2, HRD5 for logging. Sorry
for the edit.
John
KA5BJC
Distance and Bearing are automatically
determined and displayed in the Callsign tooltip, but only if both
your gridsquare and the decoded callsign gridsquare are known.
Check that you have set your Gridsquare in the JTAlert Settings
window, Station Callsign section.
DUH! Because my grid is in the standard messages (from WSJT-), I didn't pay attention to the Call sign screen (even though I did look at it for something else). Old settings probably got wiped when I was trying to solve my slow form update problem.
DUH! Because my grid
is in the standard messages (from WSJT-), I didn't pay attention
to the Call sign screen (even though I did look at it for
something else). Old settings probably got wiped when I was trying
to solve my slow form update problem.
John,
The need to set your Grid in JTAlert is historical, dating back to
the pre WSJT-X days of JT65-HF.
Already on the todo list is to abandon the need to set your Grid
& Station Callsign and use the values passed in the WSJT-X UDP
Status message.
