Currently the Callsigns window (not QSL window) only supports separate views for Lotw and Eqsl decodes. If you want to see both LoTW and Eqsl only Callsigns you will need to have 2

Provided you don't have JTAlert callsigns click handling disabled, JTAlert always sends the appropriate UDP message in response to a Callsign click regardless of the decode type.

Mike, If JTDX stops responding to JTAlert callsign click events when JTDX filtering is applied that indicates a defect within JTDX. JTAlert always sends a correctly

tnx for your fast answer! Unfortunately there is no rule. An approach that only "reduces options" but does not directly relate the province is this: Spanish Provinces EA1: AV, BU, C, LE, LO, LU, O,

Jorge, such an enhancement suggestion should include a method for determining the province of any EA call quickly enough to raise an alert. That means within a few milliseconds of decoding the call

I am using JTDX (2.2.156) with JTAlert (2.50.7). Recently I enable the JTDX filter "Show only CQ, RRR, RR73, 73 messages", to reduce clutter in the Band Activity window. This worked, but it also

It would be nice if in some new releases of JTALERT, the alert option to detect new Spanish Provinces (there are 52) could be included Thank's in Advance! JORGE - EA2DDE

I am using JTDX (2.2.156) and recently set the filter to show only CQ, RRR, RR73, 73 messages in the Band activity window. This worked great, except it also disable the POTA from decode display. POTA

Hi Laurie I am a new user to JTDX and I have been following this thread as I have a similar situation. I've checked the filters and disabled the "Prevent spotting messages

Silly me !! From times before JTAlert 2.5 I still had 'LotW OR eQSL(AG) member' ticked in JTAlert settings. That said leeds to the question if this setting can be brought up as

If you have JTAlert setup to use ACLog then the only action you need to perform for WSJTX QSOs to be sent to ACLog is to click the "OK" button on the WSJTX "Log QSO" window. This is not

I have JTAlert logging and would like to have WSJT log direct to Aclog. Can’t figure it out. WA6MBL-Bob

Peder, The Wanted Callsigns and Ignored Callsigns lists in JTAlert are stored within the main JTAlert config file so the only way to get them onto a new PC is to copy the entire

Do you have any filters enabled within JTAlert ("Filter" shown in its titlebar)? If so what do you have enabled? Filters by their nature will reduce the Callsigns displayed as decodes

OK Bill. Copying the localappdata directory to the new machine is how I would do it and what I recommend. From your experience, it would appear that something in the old JTAlert config

The window you're referring to is the "Callsigns" window, not the "Decodes" window which is totally different. That is what is shown in its titlebar text and how it is called under the View menu

A simpler alternative to using the Settings window to add callsigns is to right-click a callsign in the Callsigns window and use the resulting context menu to either add that callsign to the

Try rescanning your log file? sent via LG hand held device

Thank you very much. deni WBØTAX

click settings on jt-alert go to wanted callsigns enter each callsign if they are on after you enter the info make sure the box is checked for alert at the top go down and pick a sound from alert