Log4OM

keystrokes added to previous comment

"click in callsign field
type callsign (eg) EA7KIP
Click on Hour (while this is happening callsign is searched)
type hour (eg) 10
click on minute
start typing minute (callsign is searched again)
cursor is moved into callsign field.

As soon as I start typing the minute, the callsign is again searched, depending on how fast I type the minutes are entered at the end of the callsign, replace it or are entered in the minute field and the cursor then ends up back in the callsign field."

For some reason your beating the lookup completion, have you got a slow internet connection and what lookup[ are you using?

I tried disabling the lookup, after entering the hour the cursor jumps back to the callsign, same when entering the minute and the year, jumping back to the callsign each time. The map is also refreshed in the main window.

This happens when I change any details on the start time (end time does not refresh)

Internet connections is fibre 260mb down, 120mb up.

What lookup, QRZ, hamqth?.

What software is running in the background?

At this time nothing else running as I was just entering some old qso's manually.

At other times I have been running WSJT-X. JT-Alert and Log4OM all at once for FT8 with no issues but for now just Log4OM.

I just find it odd that the cursor goes back to the callsign field each time I change anything in the Start field and nowhere else.

I also tried with another installation on a different pc and that behaves in the same way

I am at a loss because none of the testers or me can emulate this so its something local to you.

Perhaps try a fresh download and install?

Different PC, New install, Empty database.

When I change anything in the Start field
The cursor jumps back into the Callsign field.

Really odd......

What happens here.
QSO data retrieved from intarnal and external sources are related to some parameters.

Callsign (that identifies the country)
QSO Date (that collaborate into country identification and award / award reference valid date range)
Band and mode (that are considered for awards preselections)

When changing the date field a data refresh is performed because you may have, at the new date, a different callsign country (yes, DXCC moved a lot over different prefixes during years, mainly in Russian areas) and different awards and valid references.
What is should NOT do is to move the focus away before you've completed your activities.

A valid method could be wait until the user leave the control, but the user may be satisfied of the new date and not move away from the date box for the duration of the QSO, so we didn't perform any check and we potentially save "wrong data".
Another method can be waiting a bit more before making checks, but this will affect also callsign lookup times.

The best way is to prevent focus loose, but seems the most complex one... i must check

Just reading my original post, it was on changing Day or Month that the lookup was occuring, I mentioned it was on changing the Minute, whoops....

But the explanation above summarises it correctly, and the issue I have was the change of focus on entering the date.