Date   

locked Re: AntiVirus & JT Alert 2.14.5

Michael Black
 

On Thursday, October 3, 2019, 09:05:13 AM CDT, Anthony <n2ki.ham@...> wrote:


After searching the forum, I do not find a way to bypass this "threat" found by BitDefender. As such I can not install the latest version of JT Alert.  I rolled back to  2.13.6.  Other than removing Bitdefender, any suggestions?  I can not tell BD that the file is ok on install.  Thanks!


--

Anthony N2KI


locked Re: Minor persistent glitch

Radio K0HB
 

This is from the normal (red icon) version.  I haven’t installed alternates.

73, de Hans, KØHB
“Just a Boy and his Radio”
 


From: support@hamapps.groups.io on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Thursday, October 3, 2019 2:04 AM
To: support@hamapps.groups.io
Subject: Re: [HamApps] Minor persistent glitch
 
On 3/10/2019 12:35 pm, HH Brakob wrote:

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

73, de Hans, KØHB

Hans,

I thought I clobbered that defect long ago.

What build of JTAlert are you running "Traditional" or the "Alt Layout", I couldn't tell from your image? Please test the other build type (just use the appropriate shortcut), does it also display the incorrect totals data or is the defect build type specific?

de Laurie VK3AMA


locked AntiVirus & JT Alert 2.14.5

Anthony
 

After searching the forum, I do not find a way to bypass this "threat" found by BitDefender. As such I can not install the latest version of JT Alert.  I rolled back to  2.13.6.  Other than removing Bitdefender, any suggestions?  I can not tell BD that the file is ok on install.  Thanks!


--

Anthony N2KI


locked Window size - Dock to WSJT-X

Frank C. D'Amato
 

I enabled the dock to WSJT-X, but the window of JTALERT is wider than WSJT-X v2.14.4.  I've tried lowering the number of columns, but the width remains the same.

This was not the case back on 2.12.10


locked Re: 2.14.5 Issue

Ed Wilson
 

Laurie,

This issue has been fixed in JTDX.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, October 2, 2019, 7:18:47 PM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
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?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA


locked Re: Minor persistent glitch

Michael Black
 

It's the same in both layouts....
Inline image

What exactly are those totals supposed to reflect? 

I assume the following....


sqlite> select count(*) from log where mode='FT8' and dxcc=291;
13786
 
sqlite> select count(*) from log where mode='FT8' and state='NC';    << NC is for the callsign that I selected to test.
622

de Mike W9MDB


On Thursday, October 3, 2019, 02:04:42 AM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 3/10/2019 12:35 pm, HH Brakob wrote:

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

73, de Hans, KØHB

Hans,

I thought I clobbered that defect long ago.

What build of JTAlert are you running "Traditional" or the "Alt Layout", I couldn't tell from your image? Please test the other build type (just use the appropriate shortcut), does it also display the incorrect totals data or is the defect build type specific?

de Laurie VK3AMA


locked Re: v12.14.5 Text Message Don't Work

Michael Black
 

I frequently observe that F5 does not work and have to use the menu to bring up the text messages box.

Would a debug log help figure out why this happens?  I never worried about it too much but may be related -- it's been happening for a LONG time.

de Mike W9MDB




On Thursday, October 3, 2019, 02:07:01 AM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 3/10/2019 4:24 pm, WB5JJJ - George wrote:
The F5 access to call up text messages does NOT work in the Normal layout version.  Running Win10 all updates.  I5 CPU. 8Gb RAM.  CPU load <15% with everything running as normal.  Rolled back to 12.14.4 Normal layout and F5 again works.
--
73's
George - WB5JJJ
George,

Working here in my tests. There were no changes in the code involving hotkeys.
Does the window open if you use the "View -> Text Message Window" menu?

de Laurie VK3AMA


locked Re: 2.14.5 Issue

Ed Wilson
 

Great! I am looking forward to testing it or a later version soon.

Ed, K0KC

k0kc@...
http://k0kc.us/


On Thursday, October 3, 2019, 5:48:22 AM EDT, Игорь Ч via Groups.Io <c_igor@...> wrote:


Hi Ed,

UDP replay issue is fixed starting from JTDX 140_18.

73,
Igor UA3DJY


Четверг, 3 октября 2019, 2:26 +03:00 от Ed Wilson via Groups.Io <ed.wilson@...>:

Yes, I am testing FT4 under JTDX. I will contact Igor to report this issue.

On Oct 2, 2019, at 7:18 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
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?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA



--
Игорь


locked Re: 2.14.5 Issue

Игорь Ч <c_igor@...>
 

Hi Ed,

UDP replay issue is fixed starting from JTDX 140_18.

73,
Igor UA3DJY


Четверг, 3 октября 2019, 2:26 +03:00 от Ed Wilson via Groups.Io <ed.wilson@...>:

Yes, I am testing FT4 under JTDX. I will contact Igor to report this issue.

On Oct 2, 2019, at 7:18 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
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?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA



--
Игорь


locked Re: v12.14.5 Text Message Don't Work

HamApps Support (VK3AMA)
 

On 3/10/2019 4:24 pm, WB5JJJ - George wrote:
The F5 access to call up text messages does NOT work in the Normal layout version.  Running Win10 all updates.  I5 CPU. 8Gb RAM.  CPU load <15% with everything running as normal.  Rolled back to 12.14.4 Normal layout and F5 again works.
--
73's
George - WB5JJJ
George,

Working here in my tests. There were no changes in the code involving hotkeys.
Does the window open if you use the "View -> Text Message Window" menu?

de Laurie VK3AMA


locked Re: Minor persistent glitch

HamApps Support (VK3AMA)
 

On 3/10/2019 12:35 pm, HH Brakob wrote:

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

73, de Hans, KØHB

Hans,

I thought I clobbered that defect long ago.

What build of JTAlert are you running "Traditional" or the "Alt Layout", I couldn't tell from your image? Please test the other build type (just use the appropriate shortcut), does it also display the incorrect totals data or is the defect build type specific?

de Laurie VK3AMA


locked Re: Instructions & Initial Setup DXCC Alert for Individual Bands

HamApps Support (VK3AMA)
 

On 3/10/2019 9:43 am, Mark W2OR via Groups.Io wrote:
Thank you.  That was helpful.  Even though I've been using the scan and various alerts for months now, I'm still scratching my head on one or two things (paragraph three below).  I'll figure it all out eventually.

My DXCC alert objectives are not unlike most other stations' DXCC objectives.  Thankfully, JTA continues to work perfectly for the Any Band & Any Mode DXCC alert.  There are 24 entities correctly listed in the Wanted column, and the JTA alert for this main objective appears to work perfectly.

I'm still hung up on how to configure the Second Objective: That is, to configure JTA to alert when band-specific unworked entities are decoded.  I need this alert active simultaneously for multiple bands.  In my JTA, only one band (60m) seems to have the "Wanted" column correctly populated with countries.  All the other bands have nothing at all in the "Wanted" column.  As such, this gives the impression that JTA will not alert for any of those other bands when an unworked band-specific entity is decoded.  In other words, I'm not sure how to get that Wanted column populated for all bands, remain that way, and then have the alerts work simultaneously for all bands. As mentioned above, in a few more days I'll have it figured out. Eventually.

P.S.  The Marathon alert works fine, likewise the Wanted Callsign, and Continent, and other alerts seem to work marvelously well when they are used.  This is one fantastic program !!
Mark,

You mention "
Any Band & Any Mode DXCC alert". If your setting the DXCC alert Band and Mode tracking to Any Band and Any Mode than you will never get Band specific alerts. You need to leave the tracking selector for the dxcc alert to "Individual Band".

When you are viewing an individual Band wanted list in the Settings, and you have by individual Mode tracking selected, make sure you select the mode of interest. It is very easy to have the mode selector on JT65 and if you only log FT8, than the wanted lists will appear incorrect. JTAlert does its best to remember the last mode you selected, but that only works if your not switching Mode and Band tracking types.

So I can better understand what your describing, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis. Include a note of a DXCC Band you feel is populated with Countries.

de Laurie VK3AMA



locked v12.14.5 Text Message Don't Work

WB5JJJ - George
 
Edited

The F5 access to call up text messages does NOT work in the Normal layout version.  Running Win10 all updates.  I5 CPU. 8Gb RAM.  CPU load <15% with everything running as normal.  Rolled back to 12.14.4 Normal layout and F5 again works.
--
73's
George - WB5JJJ


locked Minor persistent glitch

Radio K0HB
 

Installed 2.14.5.  Works as announced!

 

Still one minor glitch at my station.

 

The “#” column in the bottom (US State) line still reflects the same total as the “DXCC” line.

 

 

73, de Hans, KØHB
"Just a boy and his radio"™

 


locked Re: Instructions & Initial Setup DXCC Alert for Individual Bands

Mark W2OR
 

Thank you.  That was helpful.  Even though I've been using the scan and various alerts for months now, I'm still scratching my head on one or two things (paragraph three below).  I'll figure it all out eventually.

My DXCC alert objectives are not unlike most other stations' DXCC objectives.  Thankfully, JTA continues to work perfectly for the Any Band & Any Mode DXCC alert.  There are 24 entities correctly listed in the Wanted column, and the JTA alert for this main objective appears to work perfectly.

I'm still hung up on how to configure the Second Objective: That is, to configure JTA to alert when band-specific unworked entities are decoded.  I need this alert active simultaneously for multiple bands.  In my JTA, only one band (60m) seems to have the "Wanted" column correctly populated with countries.  All the other bands have nothing at all in the "Wanted" column.  As such, this gives the impression that JTA will not alert for any of those other bands when an unworked band-specific entity is decoded.  In other words, I'm not sure how to get that Wanted column populated for all bands, remain that way, and then have the alerts work simultaneously for all bands. As mentioned above, in a few more days I'll have it figured out. Eventually.

P.S.  The Marathon alert works fine, likewise the Wanted Callsign, and Continent, and other alerts seem to work marvelously well when they are used.  This is one fantastic program !!



locked Re: 2.14.5 Issue

Ed Wilson
 

Yes, I am testing FT4 under JTDX. I will contact Igor to report this issue.

On Oct 2, 2019, at 7:18 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
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?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA


locked Re: 2.14.5 Issue

HamApps Support (VK3AMA)
 

On 3/10/2019 9:09 am, Ed Wilson via Groups.Io wrote:
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?

Thanks!

Ed, K0KC
Ed,

Since JTDX with FT4 has not been publicly released (still in beta testing as far as I know), the cause is very likely something within the JTDX.

The JTAlert code for managing sending commands to WSJT-X and JTDX in response to a single-click is Mode independent. There are no mode checks performed before sending the command to the relevant application instance, FT4 clicks  should work the same as FT8 clicks.  This further suggests the problem is with JTDX.

If your beta testing JTDX, I suggest you raise this issue with them.

de Laurie VK3AMA


locked Re: 2.14.5 Issue (Edited)

Ed Wilson
 



On Oct 2, 2019, at 7:09 PM, Ed Wilson via Groups.Io <ed.wilson@...> wrote:

Laurie,

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 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?

Thanks!



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...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

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.

    <2.14.5_ScanResults.png>


The Release Notes...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA

<2.14.5_ScanResults.png>


locked 2.14.5 Issue

Ed Wilson
 

Laurie,

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?

Thanks!



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...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

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...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA


locked New JTAlert 2.14.5 available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

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...
  • Red => JTAlert for WSJT-X.
  • Blue => JTAlert for JTDX.
  • Green => JTAlert (Alt Layout) for WSJT-X.
  • Purple => JTAlert (Alt Layout) for JTDX.
See the release notes below for a full list of changes and fixes.

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...
  New Features:
    - Option to turn off State Code display after Callsign.
       (Default: OFF, Window: Settings, Section: Alerts, Wanted States).

  Changes:
    - The JTAlert "Alternate Layout" build has been renamed "Alt Layout".
    - "Alt Layout" builds of JTAlert are no longer provided via a seperate installer.
       The one installer now includes both builds of JTAlert, "Traditional" with
       menus in the title bar and "Alt Layout" with the menu below the titlebar.
       Switching to a different layout build is simply handled by executing the
       correct shortcut.
    - "Alt Layout" builds of JTAlert now use unique colored icons for the shortcuts
       and the JTAlert window titlebar.
         Red => JTAlert for WSJT-X.
         Blue => JTAlert for JTDX.
         Green => JTAlert (Alt Layout) for WSJT-X.
         Purple => JTAlert (Alt Layout) for JTDX.
    - Support for JTDX non-standard FT4 UDP decode mode identification
       character. (WSJT-X = "+", JTDX = ":")

  Fixes:
    - ADIF import window progress bar not displaying to the full width when the
       import has completed and reaches 100%.
    - Log4OM MySQL logs not being scanned correctly resulting in all entities
       (dxcc, state, etc) being flagged as needed. (2.14.4 defect)
    - Application auto-start entry "Close" checkbox incorrectly enabled when
       the "Start" checkbox is unchecked.
    - Desktop shortcuts for additional callsigns (under the Station section of
       the Settings window) created for no-longer-supported JT65-HF & HB9HQX
    - TX Mode not displayed in JTAlert titlebar status (between the square
       brackets) when JTAlert is working with JTDX.

de Laurie VK3AMA

8681 - 8700 of 34378