Log4OM

Hi All,
When the 'set QSO start time on leaving call sign field' is set to on in the options it works as expected if the callsign is manually input but if a callsign is clicked in the cluster (F8) twice to change the frequency as well as look up then it locks and sets the time to the time of initial clicking in the cluster. Just wondering is this by design or slipped through the net or known about to be corrected?
As always thanks for your work on the program. By far the best out there.

Its never been mentioned before and I have never noticed this so its probably been like that for some time, will look into it when time permits

that's a bit intricate, many events are playing with cursor current location... checking a valid fix

If it helps at all I have noticed it only does this when connected to a rig and when it has changed the frequency but does not lock the time in 'offline' mode.
Thank you for your hard work.

We optimized that in the 2.23 version.
Now the time is locked only when you press TAB / SHIFT-TAB "exiting" from callsign field, and not when clicking elsewhere on the screen
To provide a better support we also added the keyboard PAUSE button to trigger the QSO start time, so if you're hands-on keyboard you can start-stop starting date/time with a key, while if you're using mouse you can manually use the date/time lock button on the control