locked 2.14.5 Issue
toggle quoted messageShow quoted text
I just installed 2.14.5 on my system without incident. I discovered that I cannot single-click on a call sign in the call sign display in JTAlert to answer a CQ when running FT4 under JTDX. This approach works fine with FT8 under JTDX and with JTDX and WSJT-X using both FT4 and FT8. My UDP settings seem identical for both JTDX and WSJT-X.
Is this a JTDX issue or a JTAlert issue or have I configured JTDX incorrectly somehow?
On Wednesday, October 2, 2019, 05:55:09 PM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
The Latest JTAlert version 2.14.5 is now available @ https://HamApps.com
With this release there is no longer a separate installer for the "Alternate Layout" (now called "Alt Layout") build of JTAlert. Both JTAlert build types, "Traditional" (menus in titlebar) and "Alt Layout" (menus below titlebar) are included in the one installer package. Switching between build types is now a simple matter or using the correct shortcut, there is no need to install a different build. Each Build type / Operation type (WSJT-X or JTDX) combination uses a unique coloured shortcut icon.
For users who can't or refuse to read release notes, the shortcuts for each build & operation type are...
As usual the JTAlert installer file has been run through VirusTotal. HamApps.com has the link to the full analysis results. The installer file produced two false-positives. The GData warning is simply due to JTAlert being created using the AutoIT script compiler and the Trapmine warning is a machine-learning (ml) warning which is similar to the reputation type warnings seen in the past from Norton (low installed user-base). Both are false-positives, neither identifying a know infection.
The Release Notes...
de Laurie VK3AMA