Unchecking "Show DXCC, grid, etc" doesn't change anything.
WSJT-X 2,1.0
JTAlert 2.16.13
Win 7

If I double-click on a CQ in WSJT-X it the Tx 1 field in WSJT-X is populated and transmission begins.

If I double-click on a CQ in JTAlert, nothing happens.

I still use 8.1 and have auto update turned off. I want to control when an update is allowed into the QTH computer.

Tim - N8NEU
FN00ah

-------- Original message --------

From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...>

Date: 8/29/20 16:16 (GMT-05:00)

To: Support@HamApps.groups.io

Subject: Re: [HamApps] COMMENT

On 29/08/2020 11:57 pm, WN8HGZ wrote:
> Every time I have windows upgrade I have problems with software that
> was running good begins to not work properly: SOOO! I now set windows
> to up grade when I want and I hold off as long as can. Since there are
> so many parameter's to set when u first get started u don't know what
> is causing the problem. Sooooo! of its working don't fix it. I have
> found that Laurie VK3AMA  to be right on with her help, very sharp and
> thanks so much. HRD had bad  file and she gave me the answer. HRD was
> ZERO help and wanted a fee for maintenance which I found ok however: 
> I paid the fee for 2 years and they still couldn't help me  with
> certain issues. Just some thoughts and sharing my experiences .

FYI, Laurie is an OM name here in VK.

de Laurie (OM) VK3AMA

I am looking for some additional members to participate in JTAlert testing.

My expectation is that members of this group are computer savvy, are frequent users of WSJT-X and its modes, are comfortable with using JTAlert and Windows and don't need hand-holding when it comes to using Windows File Explorer and file management, installing and uninstalling applications.

The group message volume is very small, sometimes going a week without a posting, but Members are encouraged to provide feedback on any new JTAlert build posted for testing.

The main purpose of the Testing group is to provide members with early access to JTAlert releases and interim builds and to use these releases as part of their normal Digital activity to shake out any bugs or behavioral problems that may have crept in during coding and to test any new features. I don't expect members to exercise all functions of JTAlert with every build released.

Users of WSJT-X/JTDX, and one of the major loggers supported by JTAlert, ADIF, DXKeeper, ACLog, Log4OM or HRD, are needed.

Note: Users who become members of the Test team but don't contribute to any of the online discussion for an extended period (3 months) will automatically be removed from the Team.

If your interested, please email me direct (vk3ama.ham.apps [at] gmail.com) with a brief outline of your operating environment, Windows version, Logger used, if using WSJT-X or JTDX, if using multiple JTAlert instances, how long using JTAlert, etc.

de Laurie VK3AMA
   

On 29/08/2020 11:57 pm, WN8HGZ wrote:

Every time I have windows upgrade I have problems with software

that

was running good begins to not work properly: SOOO! I now set

windows

to up grade when I want and I hold off as long as can. Since there

are

so many parameter's to set when u first get started u don't know

what

is causing the problem. Sooooo! of its working don't fix it. I

have

found that Laurie VK3AMA to be right on with her help, very sharp

and

thanks so much. HRD had bad file and she gave me the answer. HRD

was

ZERO help and wanted a fee for maintenance which I found ok

however:

I paid the fee for 2 years and they still couldn't help me with
certain issues. Just some thoughts and sharing my experiences .

FYI, Laurie is an OM name here in VK.

de Laurie (OM) VK3AMA

2.16.13 (29-Aug-2020)

  *** Includes Callsign database file version 2020-08-29 (2020-Aug-29)

  New Features:

    - Auto Clear Alert Triggers: New "Auto clear triggered Alert entity after
       logging" option available for each of the 8 Wanted Alert types. When set
       this option will automatically clear an Alert entity (eg. Grid) after
       logging a QSO, thus avoiding the need to run a "Rebuild Alert Database"
       operation to remove "worked only" entities. Note: This is only suitable
       for users who don't require any form of QSL confirmation (as read from
       their log during a Rebuild operation) before an Entity is considered no
       longer needed.
       See the "Options" section of each of the "Wanted Alerts" in the Settings.

    - Alert Database Rebuild: New "Ignore QSOs before this date" option for each
       of the 8 Wanted Alert types (Dxcc, State, Grid, etc). Setting this option
       will instruct the rebuild log scanning to exclude (ignore) QSOs in your
       log before the specified date.
       See the "Rebuild Alert Database" section of the Settings window.

  Changes:

    - Country Names: Several of the country names displayed below the Callsigns
       in the main JTAlert window have been changed to reduce the truncation of
       longer names, improving readability, and to remove the ambiguity when
       similarly named countries are truncated.

    - Logging Success Popop: The display time for this popup is increased to 10
       seconds (default is 5 seconds) if one or more of the Wanted Alerts is set
       to have their "Needed" settings automatically adjusted when logging a QSO
       as per the "Auto clear triggered Alert entity after logging" new feature.
       The increase display time is to provide sufficient time to review what
       changes have been automatically applied to the internal Alert Database.