I have tried various ways, but can not seem to successfully be able to filter out all USA states from 80 to 10M.  I only want to see on the title bar and decode window are DX countries.  I've worked all states, phone, FT8 digital.  I just want to see only DX on FT8.

Tnx for your help to an Olde Ham.

Glenn

It is not possible to directly hide decodes from specific US States on specific Bands.

If you have worked all the States on all HF Bands, then those State Based callsigns will not generate the USState Alert. You could filter out those non-alerting Callsigns.
Alternatively you could hide all "NA" decodes.

There is also the Distance-Based Filter which will hide all non-alerting Callsigns below a defined distance.

de Laurie VK3AMA

On 11/11/2020 1:37 am, VE3JI wrote:

I use a Flex 6600 with 2 slices. I open Slice master that opens 2 copies of WSJT-x and then I open manually 2 instances of JT Alert which is integrated with DXKeeper. Slice master remembers the last 2 bands that I was on in the copies of WSJT-x.
Sometimes when I open the first copy of JT Alert it points to the second copy of WSJT-x and sometimes it point to the first copy of WSJT-x.  This causing me confusion as to which band I am looking at in JT Alert.  To fix this sometimes i have to close all software and start over but not always.

I always close out JT Alert copy #2 first then copy #1 then close Slices master (closing all of the WSJT-x copies) and then close the Flex hoping to keep config files the same but this does not aleays work either.

I am using JT Alert version 2.16.14 but this has been happening off and on for several previous versions.

I was wondering if any one has a clue as to how to insure that the 2 instances of JT Alert always point to the correct copy of WSJT-x

Thanks in advance
Ian, VE3JI

JTAlert instances auto-associate  themselves with the WSJT-X instances based on the running time of the WSJT-X instances. The first WSJT-X instance started will be acquired by JTAlert instance #1, the send WSJT-X instances started will be acquired by JTAlert instance #2, etc.

If the JTAlert instances are not consistently associating them selves with the same WSJT-X instances that suggests that the mechanism your using to start the WSJT-X instances, Slice master, does not guarantee application startup order.

To guarantee WSJT-X startup order you could put the WSJT-X commands into a single batch file and have Slice Master start that batch file. That would guarantee that the second instance of WSJT-X is started after the first instance. Alternatively, you could set JTAlert to auto-start the WSJT-X instances, which will guarantee startup order.

If you enable JTAlert docking to WSJT-X you will always know which copy of JTAlert is actively working with which copy of WSJT-X.

de Laurie VK3AMA

I am using the latest release of jtAlert, and I am watching the discussion of highlighting is the "73" lines with great interewst as I woud very much like to have this feature. BUt, I can find no way to turn it on. Can someone help please.

Best 73,
Bill....K5ZQ

There is no explicit option to show the highlighted "73" and "RR73", it is automatic, BUT does have the requirement that the CQ Alert is enabled.

FYI, the next JTAlert release does have an explicit setting for enabling the highlighting and has removed the "CQ Alert" requirement. This feature is only available to WSJT-X users, JTDX is not supported.

de Laurie VK3AMA

Laurie,   I'm a big fan of using the Decodes Window, and like being able to have recent option of reducing my Display Lines to zero.  I would still like to see if my QSO partner is using Text Messaging, but now I don't see the "underline".   Not exactly sure where best to show it?   I still use the Log Fields view, so maybe an underline or green spot on callsign for those online chat?   Or some indicator on the Decodes Window for those available for an online Test Message thank-you.  73, Herb WB8ASI

|

How about all of NA?


--
73
Ron, W3RJW

I have tried various ways, but can not seem to successfully be able to filter out all USA states from 80 to 10M.  I only want to see on the title bar and decode window are DX countries.  I've worked all states, phone, FT8 digital.  I just want to see only DX on FT8.

Tnx for your help to an Olde Ham.

Glenn

Then stay with the original, WSJT-X.   The clone 'developers' removed the code in the WSJT-X code base they use, so there's nothing Laurie can do to bring it back.

 

Neil, KN3ILZ

hello
you must activate in the tab miscellaneous

Denis  F8NHF

Hi Jim
On your second question, my undestanding is that this double-click will work only on stations calling CQ.
I think !
73
Paul F6EXV

I have selected colors in JTAlert and different ones in WSJT-X.

But . . . the JTAlert colors are copied to WSJT-X. For example I have the worked B4 alert a red background with yellow text. That's the way I see it on JTAlert AND WSJT-X. If I turn JTAlert off, I don't see that. Is that the way it's supposed to work?

Also, a video tutorial I watched said double clicking a call in JTAlert would trigger Tx in WSJT-X. Doesn't work for me. Is there a preference that needs to be set to make that work?

Thanks --

Jim W4GMU

I have selected colors in JTAlert and different ones in WSJT-X.

But . . . the JTAlert colors are copied to WSJT-X. For example I have the worked B4 alert a red background with yellow text. That's the way I see it on JTAlert AND WSJT-X. If I turn JTAlert off, I don't see that. Is that the way it's supposed to work?

Also, a video tutorial I watched said double clicking a call in JTAlert would trigger Tx in WSJT-X. Doesn't work for me. Is there a preference that needs to be set to make that work?

Thanks --

Jim W4GMU

Colors are very important. Why did you remove the colors from JTDX? Please put the code back into JTDX asap. I need the colors!!!

I am using the latest release of jtAlert, and I am watching the discussion of highlighting is the "73" lines with great interewst as I woud very much like to have this feature. BUt, I can find no way to turn it on. Can someone help please.

Best 73,
Bill....K5ZQ

On 10/11/2020 14:37, VE3JI wrote:

Hi All

I use a Flex 6600 with 2 slices. I open Slice master that opens 2 copies of WSJT-x and then I open manually 2 instances of JT Alert which is integrated with DXKeeper. Slice master remembers the last 2 bands that I was on in the copies of WSJT-x.
Sometimes when I open the first copy of JT Alert it points to the second copy of WSJT-x and sometimes it point to the first copy of WSJT-x.  This causing me confusion as to which band I am looking at in JT Alert.  To fix this sometimes i have to close all software and start over but not always.

I always close out JT Alert copy #2 first then copy #1 then close Slices master (closing all of the WSJT-x copies) and then close the Flex hoping to keep config files the same but this does not aleays work either.

I am using JT Alert version 2.16.14 but this has been happening off and on for several previous versions.

I was wondering if any one has a clue as to how to insure that the 2 instances of JT Alert always point to the correct copy of WSJT-x

Thanks in advance
Ian, VE3JI

Hi ian,

if you use the option to dock the JTAlert window to the WSJT-X main window it will not matter which is which.



--
73
Bill
G4WJS.

Hi All

I use a Flex 6600 with 2 slices. I open Slice master that opens 2 copies of WSJT-x and then I open manually 2 instances of JT Alert which is integrated with DXKeeper. Slice master remembers the last 2 bands that I was on in the copies of WSJT-x.
Sometimes when I open the first copy of JT Alert it points to the second copy of WSJT-x and sometimes it point to the first copy of WSJT-x.  This causing me confusion as to which band I am looking at in JT Alert.  To fix this sometimes i have to close all software and start over but not always.

I always close out JT Alert copy #2 first then copy #1 then close Slices master (closing all of the WSJT-x copies) and then close the Flex hoping to keep config files the same but this does not aleays work either.

I am using JT Alert version 2.16.14 but this has been happening off and on for several previous versions.

I was wondering if any one has a clue as to how to insure that the 2 instances of JT Alert always point to the correct copy of WSJT-x

Thanks in advance
Ian, VE3JI  

That's a defect with the clone, not JT-Alert.

Neil, KN3ILZ

Why doesn't JTALert color JTDX decodes like it does with WSJT-X?
WHen are you going to add that for us JTDX users?

Short answer. "likely never"

The JTDX people when they copied the original WSJT-X source code to produce their offering, removed the UDP code that allowed for coloring of decodes by 3rd party applications like JTAlert.

It is my understanding that the JTDX people have no intention of returning that functionality. I had to code into JTAlert explicit code to avoid sending those UDP coloring commands to JTDX as doing so crashes JTDX.

de Laurie VK3AMA

JT Alert would start up but just closed after 1 decode cycle.  I thought it might be a windows update but not sure if that is the problem or not.


--
73 Tom K9VER

If JTAlert is crashing after every startup, the cause is unlikely to be the random memory/cpu pressure issues that have been discussed.

Have you tried downgrading to an earlier version of JTAlert? Try 2.16.14

If you get the same crashing with an earlier version of JTAlert, that may be caused by a corrupt JTAlert config file, but that is very unlikely as I have never seen a corrupt config bring down JTAlert. You can try renaming the config file to say "config.sqlite.save" and then starting JTAlert which will automatically create a new config. If you still get a crash, the likely cause is interference from you PC Protection software. My money is on your Protection software as the culprit.

You config file can be found at %localappdata%\HamApps\K9VER\config\JTAlertX\config.sqlite

de Laurie VK3AMA

Why doesn't JTALert color JTDX decodes like it does with WSJT-X?
WHen are you going to add that for us JTDX users?