Log4OM

Hi all,

When a QSO is finished in WSJT-X, this not always appear in the "Recent QSO's" list... and when appeared if you need to edit it, the changes still been not refreshed in the "Recent QSO's" after saving, but openening again editing the same QSO the data you have edited are correct.

The trouble I think that is related with refreshing the "Recent QSO's" window, because closing and opening again LOG4OM the data appared correctly.

Fernando, EA7KJE

Refreshes instantly here, what Windows system are you using?

Hi,

Windows 10 Pro Version 2004 (19041.264)

I have reinstaled LOG4OM 2.6.1.0 and works perfect.

EA7KJE wrote: 09 Jun 2020, 16:31 Hi,

Windows 10 Pro Version 2004 (19041.264)

I have reinstaled LOG4OM 2.6.1.0 and works perfect.

Has to be a reason Fernando because v 2.7 works fine, please try a fresh download and install in case last one was bad

G4POP wrote: 09 Jun 2020, 17:53

EA7KJE wrote: 09 Jun 2020, 16:31 Hi,

Windows 10 Pro Version 2004 (19041.264)

I have reinstaled LOG4OM 2.6.1.0 and works perfect.

Has to be a reason Fernando because v 2.7 works fine, please try a fresh download and install in case last one was bad

I have uninstaled again 2.6.1.0, downloaded again 2.7.0.0, made a clean installation... and stil getting the same problem. No refresing when editing a QSO nor apearing the WSJT-X new QSO's.

One more time I have reinstalled 2.6.1.0 and works perfect, so definitelly something is wrong on 2.7.0.0.

Another friend of mine (EA7HTE) installed the new version on yesterday and has having the same problems...

Fernando, EA7KJE

I am running 2.7.0.0 on Win 10 Professional, and I am also seeing this same issue.

I have noticed “missing entries” in the log when closing Net Control, that mysteriously appear later. I don’t know if it happened on earlier versions but has happened with 2.7.0.0 under Win 10 Pro 64 bit (2004).

My ver 2.7.0.0 lost contact with Omnirig (1.19) this morning too, when I ran ver 1.41 in parallel everything was reading correctly in ver 1.41, I wasn’t able to reproduce the problem and it worked correctly for awhile until I closed down.

73 Dave

Running 2.7.0.0 with Windows 10 Pro and have the same issue.

Recent QSO'S seems to freeze after first wsjt-x contact is logged. But continues to upload to qrz, eqsl.
Refresh doesn't fix it. But shutting down log4om 2 and reopening does.

When loading several calls in quick succession, such as when closing a net with net control, each entry results in looking up details via an external lookup (eg QRZ.com if enabled).

The unnecessary lookups may be the cause of temporary loss of entries that appear after several seconds.

The issue issue of looking up external databases, rather than taking data from local sources (previous QSOs, net control, etc) is something I have already raised.

73 Dave