locked Re: Minor JTDX Issue With JTAlertX

Ed Wilson


Yes, just the CQ fails to appear in the RX frequency window. I suspected it might be a JTDX issue; I guess I will try to contact the author directly since he appears to know English.
Ed, K0KC


From: "Black Michael mdblack98@... [HamApps]"
To: "HamApps@..."
Sent: Friday, November 11, 2016 8:28 AM
Subject: Re: [HamApps] Minor JTDX Issue With JTAlertX

When you say "everything proceeds normally" do you mean the Std Msgs get propagated automatically and it starts transmitting on it's own without any action from you?  Just that the CQ doesn't appear on the Rx Frequency window?  If that's the case that's a bug in JTDX since it's just one message from JTAlert that triggers it.

de Mike W9MDB

From: "Ed Wilson ed.wilson@... [HamApps]"
To: "HamApps@..." <HamApps@...>
Sent: Friday, November 11, 2016 7:22 AM
Subject: [HamApps] Minor JTDX Issue With JTAlertX


Thank you for adding JTDX compatibility to JTAlertX 2.8.5.

I have been testing JTDX off and on for a couple of weeks now and have noticed a minor issue when used with JTAlertX (using the shortcut for JTDX). If I double-click on a station calling CQ in the Band Activity window, that line is transferred to the RX Frequency window. If I double-click on the same station in the JTAlertX call sign display, the line is not transferred, but otherwise everything proceeds normally and I am able to call that station. If I test this action in WSJT-X and JTAlertX, the line showing the station calling CQ is transferred when double-clicked in either WSJT-X or in the JTAlertX call sign display.

Obviously this is not a big deal, but it would be nice to see consistent behavior between the two applications.

Ed, K0KC


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