Validation of QSOs before saving

Feature Requests
1

My sister is just made her first 25 QSOs since upgrading to her General class license. I suggested WRL as her logging system and it works well, but for a beginner, it is missing some guardrails.

She was able to enter an invalid callsign, in fact, it was just the number “5” as the callsign and WRL saved it. Also, WRL does not require the frequency to be entered. It would be great to require all the basics that are needed for QSO verification before being able to save a QSO to the log.

I talked her through fixing up the errors in the log and she knows going forward what to do, but for newbies, guardrails would be great!

Thanks!

1 Like
2

I so agree with this. I can’t count the number of times my dyslexic fingers have typed G instead of 6, O instead of 0, E instead of 3, etc. :sweat_smile:

However, with that being said, with all the different varieties of callsigns from all over the world I doubt they could come up with a solution for my specific issue, but as far as missing fields that would hopefully be something they can help with.

1 Like