While operating GB18NH I noticed that if I entered a QSO (hit return) before the QRZ.com lookup had finished, then the locator found in the QRZ.com lookup is inserted in the blank/new QSO log line.
For simplicity, let us assume there has been no QSOs entered in the log, so the first QSO entered would be serial 001;
- The operator, with CamLog open in front of them, calls CQ and 'M1BXF' responds.
- The operator enters 'M1BXF' into the callsign box for serial 001 and hits TAB.
- CamLog looks up 'M1BXF' on QRZ.com to fetch the locator.
- The Operator completes QSO 001 and enters it, by hitting return before the QRZ.com lookup is complete.
- The locator found for 'M1BXF' on the QRZ.com lookup is entered into the locator box for serial 002.
I believe this will only be noticed while on a slow internet connection. It is also likely that the locator for QSO 001, which is entered into QSO 002, will be overwritten when the operator enters a new callsign into QSO 002 and hits TAB, which will trigger another QRZ.com lookup and will overwrite the locator.
While operating GB18NH I noticed that if I entered a QSO (hit return) before the QRZ.com lookup had finished, then the locator found in the QRZ.com lookup is inserted in the blank/new QSO log line.
For simplicity, let us assume there has been no QSOs entered in the log, so the first QSO entered would be serial 001;
I believe this will only be noticed while on a slow internet connection. It is also likely that the locator for QSO 001, which is entered into QSO 002, will be overwritten when the operator enters a new callsign into QSO 002 and hits TAB, which will trigger another QRZ.com lookup and will overwrite the locator.