I read that in the RN's before installing, but didn't realize it would affect the dialog boxes for settings so greatly. The menu's can't be scrolled, so the only way to change many pages is to reduce

As you can see, the screenshot from v2.50.6 is how I've had the Callsign window configured since 2.50 came out at 145%. This is on a 3rd monitor about 5' from my chair and needs larger text to be easi

To rescan the adif, goto Files >> Settings >> Colors and on the right about 2/3 down is a button to do this.

I have seen this also in recent days/weeks. I also noticed that WSJTx does NOT honor a B4 status on some stations, thus triggering the wanted status on to JTAlert. Nothing special about the call or an

Rebooting only fixed the minimize option. The root cause was having JTA "docked" to WSJTx on top. It was like the middle option (JTAlert always on top of other windows) was checked, which it wasn't. I

Running 2.50.6 and found that the chat box is now always on top. That option is NOT checked and I even toggled it to make sure. It also will NOT minimize as well. I have to uncheck Position Locked so

Since it appears so strong (red bars), do you live near a hospital, clinic or any commercial establishment? Is it 24/7? If you turn your antenna, does is fade in/out? Is it just on 50.313 or up and do

I believe that was a default setting before. I keep forgetting about the "gear" in the Callsigns window after I initially set thing up. Would be nice to see that temporary ignore (session) as a defaul

Prior to the new redesign, I had the option to ignore a callsign during this instance of JTA until a restart or permanently. This was really useful when you start to get annoyed by an alert for a cert

I paused my updates for 7 days to give MS time to fix their problem. v5.0.7 will reinstall itself almost immediately after Updates downloads it. It's listed as a "security" update so it does not need

I paused my updates for 7 days to see what happens. Hopefully, no surprises for the next week.

Did the roll back to v5.0.6 as Laurie recommended. So glad he was up while we were sleeping and had a solution at the get-go. So I fixed the problem, until MS want's to update me again. I hope they ro

Dennis: Your JTAlert is over a year old. Perhaps there have been changes in your logging program that is no longer compatible with such an old version of JTA. Current is 2.50.1 and requires dotNet v5

I've been caught by this a couple of times. I start typing a response to an F5 message while calling CQ. When a NEW station calls me back, their call replaces the call in the DX Call (WSJTx) and also

I removed my original post as it was posted to the wrong group. Sorry. Been working with Laurie on another issue (obviously) and old brain cells failed me on this post.

That works very well. I was just was not totally clear as to what the options did. A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better. Again a g

Thanks for you suggestion Joe. But I desire to use a minimalist single line display for this as with earlier versions. I'll live with the pop UNDER for lower priority items to keep it to one line. Don

Caught it happening. Screen 1 is the calling me on top of 2 announced wanted prefix callsigns. Screen 2 is after I clicked the "x" and it shows what was hidden. Screen 3 same as 1 with different stati

The 1,2,3 are positions from the left side of the Callsign Window. I sent you a support request so you will have my settings and such to check.

I have a very strict selection process in JTAlert. I only see stations that I've not worked before that are LoTW users. This would include any other alerts as well. So I don't see B4 and non-LoTW user