locked Re: JT-Alert & HRD Compatibility

Jim - N4ST

Nope, I still have an issue with the country being set to blank for QSOs entered into HRD Logbook HRD 5.24 by JT-Alert that are subsequently manually updated.

--- In Ham-Apps@yahoogroups.com.au, "Jim" <newsgroup@...> wrote:


I posted about 6 hours too early.
HRD 5.24 was released and it fixes the two problems I mentioned below.

The good news is 5.23 isn't the last free version!

Jim - N4ST

--- In Ham-Apps@yahoogroups.com.au, "Jim" <newsgroup@> wrote:

I am using JT-Alert 1.6 and HRD 5.23.012
I have found two compatibility issues:

1) Editing/Updating any part of the the HRD logbook entry for a US QSO results in the Country being set to blank. This only occurs for JT-Alert QSOs with the United States. This may be because JT-Alert writes the entry as United States of America initially, while HRD uses only United States.

2) If HRD Callsign Lookup is enabled (QRZ Subscription), it takes ~20 seconds for the update to complete. This only happens on the JT65 QSOs and only if Callsign Lookup is enabled. This happens about 95% of the time, but not every time.

Not sure where to point the finger, JT-Alert or HRD, but the issues only occur with the JT-Alert recorded QSOs.

I don't know how many changes (if any) will be made in the HRD Logbook format when the paid version (6.0) is released, but there will likely remain many users of the free HRD 5.23 version.

(Using 64-bit Windows 7 on 3GHz Core2 Duo)

Join Support@HamApps.groups.io to automatically receive all group messages.