This defect has been identified, corrected, and tested. It will be in the next public release. de Laurie VK3AMA

It is starting to look that way. I just now double-checked, the Manager is compiled as an "Any CPU" executable which means it should run on both 32bit & 64bit systems. Perhaps it is WIn7 that is the c

Post an image showing the results. de Laurie VK3AMA

Google "how to recover off-screen widow" de Laurie VK3AMA

That's the problem. Without the Manager running, nothing will work. It is critical to JTAlert operation. de Laurie VK3AMA

Robert, files received. Thanks. Check you email, I have sent a new build to try. Let me know if it corrects the Callsigns window closing and opening. de Laurie VK3AMA

In addition to my last message, the duplication of the Caller callsigns, one in the main view, and one in the Callers view, is similar to how WSJT-X displays decodes. A Calling station will show under

The Callers area, by design, only contains stations calling you, it does not auto-clear like the main view at the end of a period. It allows you to see past Callers that you have not worked. Its a con

You beat me to my response, which essentially says the same, but not as clear in the detail. de Laurie VK3AMA

If you want single line only, which will automatically show a vertical scroll bar when the number of callsigns exceeds the space available, you need to have the Callers display position set to either

All UDP comms, Sound output and opening of the new 2.50.0 windows, like the new Help->About window are controlled by the JTAlertV2.Manager.exe process located in the pluginsX sub-directory of your JTA

Good stuff! Thanks for updating the group. I think I will start recommending that HRD users who are experiencing unexplained slowdowns or errors that they upgrade their log to Maria and no longer sugg

The release notes had all the hotkey assignments for opening the different windows. Also, you can go old-school and use the View menu of the main JTAlert window. Look for the "stared" menu entries. de

No need to be sorry. Not a waste of time. Any responses I post to the group are then in the message archive for future generations. de Laurie VK3AMA

Do you really want an answer? The difference is that my screen-capture shows the checkbox display scrolled down to reveal the settings that were not in view. Note my image had a red rectangle around t

That was one of the changed settings that didn't get documented. I changed the default from single-click to double-click during development to avoid the numerous inadvertent initiating of QSOs while I

From the Decodes window help file, Settings topic.... Change the setting to wither "Delete All ..." or "Delete Old ..." will dramatically reduce your database size and improve the performance. de Laur

#1, Yes. After a JTAlert Alert database rebuild, JTAlert knows all there is to know about what alert-able entities (countries, states, zones, etc) you have. The rebuild needs to be rerun when your mas

Do you have the ACLog API enabled? If not there will be no logging. See the JTAlert Help File, "Settings -> Logging -> ACLog" topic. ACLog must be running and have its TCP API enabled. If you still ha

OK Jo9e. I was unaware that DXKeeper flagged non-AG QSLs as confirmed. I will need to extend JTAlert to account for that. de Laurie VK3AMA