Unchecking the "Ignore grid square" box made no difference. -- Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us

The call I added was WB0CPW. Just transmitted again. Still cyan. Other calls on the same band in the same sequence turned purple. -- Jim Reisert AD1C, <jjreisert@...>,

I just added another call, WB0-something. Never worked before, ever. Originally Cyan background. Did not turn purple on his next transmission. I added the call, then got interrupted with my

I have "Ignore Gridsquare" checked, nothing else. I don't see any way to select worked B4 bands. -- Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us

What Band/Mode/Grid options do you have set for the "Worked B4" Alert? de Laurie VK3AMA

"Alert when decoded Callsign worked B4" is checked. In general, I probably want that unchecked. I assume if the call is on a different band it won't be considered "worked before" and will

No, I have only worked him on 30m FT8, but the spots were on 17m and 15m. They did not highlight. I just added K2HT. He's calling CQ on 80m. I have a 15m QSO. The new call is being highlighted

If a callsign is getting its background colored than it is because that Callsign is generating an Alert. If you don't want the coloring then you will need to turn off that Alert type.

Does NE9U already exist in your log for those 2 bands? If so he wont be alerted unless your enable the "Alert when decoded Callsign worked B4" setting for the Wanted Callsign Alert.

Another call I added isn't working either (KB0QEF). I am seeing other callsigns highlighted in the same receive sequence. Is there a limit as to the maximum number of wanted callsigns supported by

For some reason, the call NE9U is not being highlighted as a wanted callsign. It's in the list. Other calls are being highlighted. I saw the same problem on both 17m and 15m. I tried removing it

At 86 that is OK. You deserve it. Randy K4ODL

I know I asked about this before but it appears I have not done something correctly. In JT Alert when a South American station appears the box in JT Alert has a yellow background. While not a problem

Trying to make this bullet proof. Imagine you start multiple JTAlerts -- then start my app. You don't have sufficient information to tie each to a specific instance. I do remember the PID...but

Yes...that work's...but you said it won't work in the future. Mike

Did you try the /name=XXX command-line parameter? From Process explorer... de Laurie VK3AMA

Why not just enumerate the already running processes when you program starts to get the current PIDs (and the process names, main window Hwnd, command-line, etc) for the applications your interested

But I want the distinction to last over a restart of my app too...and the PID won't do that. The PID isn't a guaranteed association to any specific named instance Only thing I have to work with is

Mike, You can already do that. By design JTAlert ignores any unsupported command-line options. However, that will not always be the case and should not be relied

If I want more than a basic QSO, I do not use any JT/FT modes. Simples! -- 73 de Guy G4DWV 4X1LT