Page 1 of 1

"Recent QSO" slow to open—is there a better way?

Posted: 27 Sep 2024, 13:57
by Ki1n
Opening a recent QSO takes an increasingly longer time that seems to be reset after program shutdown and restarting. Opening recent QSOs can be handy when engaging in discussions when an additional stations breaks into an existing QSO. Is there any way to avoid increasing delays in opening recent QSOs?
This scenario occurs when a 3rd (or 4th) station wants to join an existing QSO. I then close the original QSO, open another with the new station's call sign, and then reopen the prior QSO using the "recent QSO" window—I do this to enable note taking for each station in the QSO. The existing "Net" function doesn't seem practical for spontaneous additions to a QSO in progress.
This lag-time problem is increasingly apparent after awakening the system from a sleep cycle. The access time for a recent qso decays sequentially from "almost instantaneous" to 10-15 seconds, at which point I restart Log4OM to reset the decay time.
I'm using Version 2 with Win 11 on an i7NUC with 6 cores/12 threads 4.7Ghz connected to web via WiFi 5Ghz.

-- Bob - Ki1n

Re: "Recent QSO" slow to open—is there a better way?

Posted: 27 Sep 2024, 14:01
by G4POP
Bob,
I am not quiet understanding which window is slow to open, is it the 'Edit QSO' window that is actioned by a double click on the old QSO in the recent QSO window?

Also actual version number please - See help/about

Re: "Recent QSO" slow to open—is there a better way?

Posted: 28 Sep 2024, 14:01
by Ki1n
Hi Terry.
Yes, I was referring to opening the QSO in Recent QSO panel. Version 2.33.0.0
-- Bob - Ki1n

Re: "Recent QSO" slow to open—is there a better way?

Posted: 28 Sep 2024, 14:15
by G4POP
Ki1n wrote: 28 Sep 2024, 14:01 Hi Terry.
Yes, I was referring to opening the QSO in Recent QSO panel. Version 2.33.0.0
-- Bob - Ki1n
I dont understand why you need QSO edit windows opened so often

I take part in many nets and usually use the Net Manager for regular ones and add the comments in the field provided.

However if I am in an informal/impromptu net I add comments before saving each QSO in the input window 'Comments' or 'Notes' fields and then save the QSO ready for anyone else that may want to jump in!

I enter the next joiners details and comments and save that QSO

If on the very rare occassion need to add something to a previous record that is the only time I use the edit dialog.

If you must use the edit window in such a manner then I suggest that instead of clicking the 'Check' (save and exit) icon that you click the Floppy disk icon which saves the edit but leaves the window open. Then double clicking another QSO in recent QSO's will change the edit window data and this will save the constant opening and closing of windows

Re: "Recent QSO" slow to open—is there a better way?

Posted: 28 Sep 2024, 17:21
by Ki1n
Thanks Terry.
If you must use the edit window in such a manner then I suggest that instead of clicking the 'Check' (save and exit) icon that you click the Floppy disk icon which saves the edit but leaves the window open. Then double clicking another QSO in recent QSO's will change the edit window data and this will save the constant opening and closing of windows
I have tried that but the delay in accessing another recent QSO persists for each accessed QSO. If I logout and restart, the access time is very quick, but that speed diminishes when using the technique days later.
-- Bob - Ki1n

Re: "Recent QSO" slow to open—is there a better way?

Posted: 29 Sep 2024, 07:32
by G4POP
Try turning of Voacap

Re: "Recent QSO" slow to open—is there a better way?

Posted: 01 Oct 2024, 17:35
by Ki1n
G4POP wrote: 29 Sep 2024, 07:32 Try turning of Voacap
Thanks for that suggestion Terry. I tried that but it didn't seem to help. I tested opening a recent QSO after restarting the program and got the following with repeated attempts:
Program startup 09:30 (local time) 5 seconds (time to open)
16:22 28
Next day 13:17 31

It seems the average opening time of recent QSO with Voacap turned off is about 30 seconds with the program having been running a while. If I have just restarted the program it only takes 5 seconds for the first attempt.
Any other thoughts?
-- Bob - Ki1n