Problem with 2.5.0.0 and INBOUND JT MESSAGGE

[LU1DA]

Hello, after updating to version 2.5.0.0, a problem appeared with the [INBOUND] JT MESSAGGE.
Log4OM is unable to receive the data from JTDX,but the [INBOUND] ADIF MESSAGGE continues
working well,and save the contact in the log.
I have not changed ports, check them and they are correct.
Before updating it worked perfectly.
The other functions are ok.
Someone with the same problem?
System info:
WIN10 64 1909

[LU1DA]

I was reviewing this problem, and discovered that it only happens when log4om program is minimized in the tray, when it is maximized on the desktop it receives the info of the UDP port.
A bug?

[OZ2LC]

I have the same problem aswell

[OZ1RE]

Yes. I have the same problem. Importing QRZ-information seems to work unstable.

[EA1IVQ]

The same problem happens to me too, so go back to v2.4.0.0

[NN7D]

Why would you expect to see the DX callsign forwarded to Log4OM from JTAlert, if Log4OM main UI is minimized? What am I missing?

Doug
W7DRM

[IW3HMH]

We prevented Log4Om from UPDATING main user interface when the program is minimized to traybar, as the application is stealing focus from the user interface in top view (usually WSJT, JTDX or similar) making an annoying issue.
All other features should work normally.

[OZ2LC]

Why would you expect to see the DX callsign forwarded to Log4OM from JTAlert, if Log4OM main UI is minimized? What am I missing?

Doug
W7DRM

If your Grid hunter and some calls you with no Grid , it good it shows that info in Log4OM
not every on have multi monitors , that why it should work

[LU1DA]

We prevented Log4Om from UPDATING main user interface when the program is minimized to traybar, as the application is stealing focus from the user interface in top view (usually WSJT, JTDX or similar) making an annoying issue.
All other features should work normally.

Thanks for the answer Danielle.

Jorge
LU1DA