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

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

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

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

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!

Ed, K0KC

k0kc@...

http://k0kc.us/

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>

• 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.

   

How's about we also add "Offline" to the text window status in addition to "Online".

I find myself staring at it wondering if it's been updated or not.

Is that possible?

de MIke W9MDB

Instructions & Initial Setup DXCC Alert for Individual Bands

If anyone knows of written instructions for the above, kindly share them here.  Thank you.

Background:  I thought I had figured out this alert setup many months ago, as it seemed to be working, but apparently I was wrong.  When I check the Wanted DXCC settings, for Individual Band, most all the bands tracked are BLANK in the "Wanted" window, even after checking the Band Enable and Select box, and after completing a Scan Log and Rebuild function.  I'm missing some basic setup procedure here, and instructions would sure help.  The settings for "Any Band" "Any Mode" seem to be fine.  I just need instructions for setting up for individual bands, including needed entities for 60 Meters and needed entities for 160 Meters, two bands where I chase DX entities individually, aside from all-band DXCC.  Thank you.

Yes, I am using JTA v.2.14.4, downloaded after the revision to the initial release.

Thanks for your reply.  Its a mute issue at this time as I worked and confirmed another OR station.

Thanks for your help and most of all thanks for a wonderful product.

Beat 73
Al
W1JHU