Anywhere on decode window crashes it.

I also restart jtalert every time it crashes just decode window.

Thanks for posting the actual error, that helped isolate the problem.

A google search confirms this common problem with Chrome and other VNC type apps.

I have modified the code to capture the error and perform a retry when pasting the decodes callsign onto the clipboard. Check your email (in about an hour) I will send a new JTAlert build to test.

Also, when this happens, there is no need to restart JTAlert. The Decodes window is a standalone executable so you only need to reopen it from JTAlert.

de Laurie VK3AMA

Laurie before I go and mess anything else up, do I delete that via the software or is it a file I need to located in a folder?

You have to manually delete the config file after first stopping JTAlert.

Refer to my original post https://hamapps.groups.io/g/Support/message/31591
The help file topic referenced in that post tells you where your config file is located.

de Laurie VK3AMA

All of a sudden the bottom half of my JTALert disappeared.

JTAlert menu, "View -> Show Log Fields".

On 15/09/2020 3:52 am, JoAnn Donaldson via groups.io wrote:

I turned OFF CHECK BEFORE and now it logs successfully.

How are you turning off the B4 check in JTAlert?
It is not possible, it is permanently enabled, there is not setting for turning B4 checks off.

What did you change that made logging work?

de Laurie VK3AMA

If I'm not mistaken you don't get very good caching on a remote network file by default.

Mike

Which is why JTAlert is optimized to minimize direct access to Log files, either locally or remotely.

JTAlert will only perform a direct access of a log file in the following circumstances...

1. When a callsign is FIRST decoded to perform a B4 check for the current Band/Mode.
   
   
2. When confirming a QSO was logged by reading the log. Past bad experiences with other loggers has shown that the status reported by the logger (via its api) after logging may not be correct and cannot be relied upon. HRD was notorious for reporting logging success when the QSO was never logged. Direct reading of the log avoids that.
   
   
3. When performing the Alert database rebuild.

de Laurie VK3AMA

Besides I have already figured out how to solve my problem with JTALert NOT logging to ACLog. It seems that when JTALert does the check for Worked Before that is when ACLog pops the error message and the Log entry is deleted. I turned OFF CHECK BEFORE and now it logs successfully. I never understand why JTALert needed to remind you that you have already worked a station before when WSIT-X already does by turning the contact GREEN.

   I suspect the timing issue is ONLY with the Before Check. I am running ACLog on a separate computer thus have to use the Manual Mode to access ACLog. Also do not understand why JTALert needs a PHYSICAL Path to the database when the N3FJP API gives the Client all the access it needs.

So put this thread asleep. I have found a flaw in how the BeFor Check is done when ACLog is on a separate computer. I found a work around for the flaw. If the Developer wants to correct this, I am more than willing to tests an update.

JoAnn Donaldson - AB8YZ 

Sorry, buy your wrong on so many fronts.

• First, there is nothing to fix, there is no B4 flaw to correct.

• What is this error message that ACLog is showing? Post an image of this ACLog generated message.

• WSJT-X reporting of B4 is independent of your ACLog log file and can be grossly out-of-sync with ACLog. JTAlert does its B4 checks against your primary log, ACLog, not the WSJTX log file which at any time could be empty, truncated or missing.
  
  
• The Timing adjustments your referring to have NOTHING to do with B4 checks. It used used purely for the QSO logged success checks. This is why the settings entry is under the "Logging" section (funny that).
  
  
• The ACLog API is very inefficient when performing many Callsign lookups (for the B4 checks) at the end of a busy FT8 period where there may be 20, 30, 40 or more callsigns to check. Direct querying of the Log file is the quickest technique.
  
  
• The ACLog API doesn't allow for custom sql queries that JTAlert uses, so direct log access is needed. This applies to all the supported loggers, not just ACLog.
  
  
• You have slowed things down further by having the ACLog file on a different PC than JTAlert so network latency is introduced further slowing log file reads.  JTAlert does cache (in memory) the results of the slow disk file lookups, but there will always be at least one physical log lookup when a callsign is first decoded.
  
  
• The Alert database (used to determine what alerts a callsigns/decode generates) requires direct access to the Log file in order to run the many hundreds of sql queries needed  to rebuild the database. The Alert database is used for high-speed determination of what alerts are triggered, it is impractical to run multiple queries (if even possible) via the ACLog API to check if a Callsign is a needed DXCC, State, Grid, Prefix, etc, at the end of a FT8 period. This in-memory database is used.
  

de Laurie VK3AMA

Laurie before I go and mess anything else up, do I delete that via the software or is it a file I need to located in a folder?

I reboot win 10 every few days. Rebooted again no difference. Anywhere on decode window crashes it.
I also restart jtalert every time it crashes just decode window.

@JoAnn Donaldson
Don't worry, that's an honest mistake. It got me a couple of times, as well. It's not always apparent that some settings are contained in the header lines, in addition to the sub-categories.
Roger
AC6BW

It totally ignores my call sign.  No highlighting or change of color and doesn't play the .wav file.  Other times it works fine.  No detectable pattern to when it works or doesn't.

When it does work it often picks up on the call sign when the other person sends a 73.

What Alert filters do you have set?
It sounds like the stations calling you are being filtered out because they are not passing the Alert filters.

de Laurie VK3AMA

As to smaller pictures. that is easy to accomplish.

Download the free Microsoft picture resizer

https://www.microsoft.com/en-us/p/image-resizer-for-windows-10/9nwwmh081ddb?activetab=pivot:overviewtab

Once installed, all you have to to is select one or more pictures you have saved on your computer, right click on it/them and then select 'Resize pictures.' When the window opens up, you choose the size. I have found that to be one of the most useful tools for many years.

John, WB9VGJ

As soon as I remote DT into my win 10 box, decode window crashes with an exception when I click on it remotely. Says clipboard operation failed.
Everything else is ok. 
2.16.13, win 10 home 1909, RD 1.5, other end is Android 9 S6 tablet (also crashes on S10e). Nov 5,2019 version.
Also crashes on MacBook Air 2017 with Edge or Chrome extension.
Not a big issue. Just fyi

I remote desktop into my Ham PC 99.9% of the time, I rarely sit in front of the PC, without this problem. Admittedly I am not using Chrome. I am not sure what could be the cause. This is the first report I have received of this behavior.

How long since you restarted your Win10PC?

What part of the Decodes window are you clicking on?

Please post a capture of the error message window. That will help with diagnosis.

de Laurie VK3AMA