Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If the user enters a QSO before the QRZ lookup is finished, the locator appears in the wrong location #25

Open
m1bxf opened this issue Oct 2, 2018 · 0 comments

Comments

@m1bxf
Copy link

m1bxf commented Oct 2, 2018

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;

  1. The operator, with CamLog open in front of them, calls CQ and 'M1BXF' responds.
  2. The operator enters 'M1BXF' into the callsign box for serial 001 and hits TAB.
  3. CamLog looks up 'M1BXF' on QRZ.com to fetch the locator.
  4. The Operator completes QSO 001 and enters it, by hitting return before the QRZ.com lookup is complete.
  5. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant