cwhelchel/hunterlog

Add support for manual entry of QSO details.

Closed this issue · 1 comments

cwhelchel commented

From #2

Entering data
○ Not an issue for clicking on parks but for manual entry:
§ Callsign should uppercase
§ Mode should have a dropdown
§ Input validation ?

Expected new behavior:

  • Input callsign (default uppercase)
    • Lookup activator on focus change
  • Input mode
    • unsure if I want to have a drop down or validate this. Who's the mode authority? ADIF spec, POTA, someone else?
  • Input park
    • lookup park details on focus change

Allow spotting from here? Not sure if that will work

cwhelchel commented

618cff0 adds a rudimentary support for inputting QSOs manually. When a call is entered it displays that callsigns activator info. When a park is added it displays park info and sets grid square to parks grid square. It also sets STATE field if it can.

FREQ (in kHz - like pota.app), Mode, RST, and others are not validated at all.

Spotting does work the manual inputs. So if someone is at a park and not spotted you can spot via the inputs.

I expect there are issues with this but it is somewhat usable. Any bugs should go in new bug reports.