I would like to report this as working now in ver 2.01 #22810 Thanks Steve M0ZEH Sent from Mail for Windows 10

Nope sorry a single click to focus JTalert followed by a single click on a cq’ing call sign does not work with jtdx As for call sign history if I enable this in settings>window>decodes history

For the curious, this is how I frequently run the Decodes History when I'm just interested in answering CQ's. I have the CQ column visible so I can see if a local is calling DX so I can

Thanks Laurie, I am always happy when an observation does not turn into an embarrassment because I have missed something in the documentation or similar. 73, Björn SM7IUN Den sön 24 mars 2019 kl

James, Try this, single click the JTAlert window to make it active, then try a single click on a callsign, does that work. My thinking is that the single-click may be getting

Yes this was my understand as well if I’m not mistaken JTalert is written with AutoIT the problem however I’m having is no matter if it’s single click or double click or any click at all on a

Double-clicking was replaced with single-clicking starting with version 2.11.4 (18-JUN-2018) The double-click detection was always problematic for some people. The code used to

Thanks again! That worked! -- John P. WA2FZW

I have been using JTalert for a while but some Where down the line I lost my ability to double click on cq’ing stations I should mention I’m using jtdx with JTalert jtdx ver. So right now I do

Thank you! Will fix that. Jack AK7O Sent from XFINITY Connect App

Jack, The answer is simple, you have the "Do not show Worked Before ...." filter set. When running with your config this is what I see...

The reason that you don't get the Log Fields display on the second instance is that by default, the display is not shown. You need to enable its display via the View menu. The

Sent. Thank you, jack AK7O Sent from XFINITY Connect App

OK, Something is not right, I will need to see your JTAlert session data. Please do the following... Enable debug recording via the "Settings -> Enable Debug

Sent from XFINITY Connect App

Did you change your call sign in ACLog settings?

Thanks Laurie! But while I have your attention, can you explain why I don't get the logging information section on the 2nd instance of JTAlert. I also noticed there was a checkbox somewhere in the

John, This is a defect in the command-line parsing JTAlert performs to determine the --rig-name, which is used to target the correct WSJT-X config to determine the UDP port

Fred, The Callsign should not matter. Is JTAlert showing a Success or Failure message after logging? Does the ACLog path shown by JTAlert (in the Settings)

You don't, Provided the Station decoding your callsign has the Callsigns database installed, they will automatically see that you are eQSL(AG) and LoTW. There is nothing you can