Thanks so much Laurie.  Having fun this evening using the Decodes Window underlining for text to quickly say thanks for the QSO, and tossing in any other comment if we make a connection.  Makes a good connection beyond just the basic QSO.   My friend often asks me if I'm on my FAX machine rather than on my radio. LOL

I usually don't have enough monitor real estate to have that window open. Will play with it.

73, N0AN

Hasan

FYI, you can restrict which columns are displayed in the Decodes window, right down to a single "Callsigns" column if desired.

de Laurie VK3AMA

On 18/11/2020 4:17 am, Torsten - DL9GTB wrote:

unfortunately for a long time I have had to find out again and again that the LOTW data is often incorrect or not up-to-date. How can I improve this?

73 de Torsten - DL9GTB

Torsetn,

Do you still what me to look into this for you? If so, I will need an example Callsign (one is enough) that is being reported incorrectly from JTAlert. I can't do any investigation without a problem callsign to examine and trace through the different source files and the scripts used to generate the Callsigns database.

de Laurie VK3AMA

Jtalert loads a arid file but I can’t find at time this file or when I do won’t load to LOTW. Driving me nuts

The JTAlert Settings, "Logging -> Standard ADIF File" section, shows you where the ADIF file is located. You can use the Select button which opens a selection dialog from which you can copy the File location from the top navigation area.

eg.



de Laurie VK3AMA

dear colleague, please tell me how this alert is turned off. thanks qrv atte LU1wh

The Release notes for the new JTAlert version has the answer...

    - WSJT-X Decode Highlighting: "73" or "RR73" decode highlighting no longer
       require the CQ Alert to be enabled. A dedicated setting is now available.
       See the "Applications -> WSJT-X / JTDX" section of the Settings window.
       Note: This and other color highlighting is not available for JTDX.

de Laurie VK3AMA

I was quite surprised and pleased when I heard an audio announcement for a new state for my WAS. When I looked at the JTAlert decode listing, it was full of calls as the band was very busy and my "new state" callsign was actually below those that were displayed on the four decode lines and was off the screen. I think it is great that the audio announcement data reads all of the decodes, not just the ones that are displayed. Everything appears in the decodes window, of course. This is another reason to keep the decodes window open.Thanks, Laurie.
73,
John W9ILY

Good stuff.

BTW, you can have the main JTAlert window set to no display lines and decodes will continue to be displayed in the Decodes Window and Alerts will still be generated. That is how I run JTAlert here.

de Laurie VK3AMA

I can confirm this defect.

The error is triggered when changing the "Highlight excess DT" threshold value in the Settings when the Windows regional-settings utilizes a non-dot for the decimal separator.

It has been corrected for the next release.

de Laurie VK3AMA

--

I was quite surprised and pleased when I heard an audio announcement for a new state for my WAS. When I looked at the JTAlert decode listing, it was full of calls as the band was very busy and my "new state" callsign was actually below those that were displayed on the four decode lines and was off the screen. I think it is great that the audio announcement data reads all of the decodes, not just the ones that are displayed. Everything appears in the decodes window, of course. This is another reason to keep the decodes window open.Thanks, Laurie.
73,
John W9ILY

Perhaps you can shed some light on what ‘this alert’ is 

Have you signed your adif file with TQSL before uploading ?

On Thu, Nov 19, 2020 at 02:19 PM, HamApps Support (VK3AMA) wrote:

The full release notes entry reads...

    - Decodes Window Online Indicators: Callsigns that are online for text message
       receipt will be shown with an underline, the same as the main JTAlert
       Callsigns display. A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.

This applies to the Decodes Window only. You need to look in the Decodes Window Settings.


de Laurie VK3AMA

Thank you
I have spent days trying to find that.
Barry

I tried to open the Decode Window (F9) and when entering in the settings and trying to set the threshold to 1 sec, I got the error message..
See the attached file for the message

73 André VE2WNF

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA

Hello Laurie,  I tried to open the Decode Window (F9) and when entering in the settings and trying to set the threshold to 1 sec, I got the error message..
See the attached file for the message

73 André VE2WNF

Does not work. Would not trans decoded call to WSJT-x.

 

Reloaded 2.16.6 to get back on the air.

 

What does not work? Please be descriptive with your fault description, avoiding abbreviations or slang.

de Laurie VK3AMA

New feature listed, but I can't find where to turn it on:

2.16.16

A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.

TIA, 73, N0AN

The full release notes entry reads...

    - Decodes Window Online Indicators: Callsigns that are online for text message
       receipt will be shown with an underline, the same as the main JTAlert
       Callsigns display. A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.

This applies to the Decodes Window only. You need to look in the Decodes Window Settings.


de Laurie VK3AMA

Mark