Yesterday I participated in the VA QSO party (new ham, first ever QSO party). I didn’t even know then that Polo had added experimental QSO support, so I quick logged on paper. When I found the QSO party support, I put my logs after the fact into Polo. However, When I put 2 in the “Our #” field to log the sequence number for the second QSO after the fact, then pressed save, the app crashed. I was only able to add my QSOs by leaving the “Our #” set to 1 each time.
Also, the “Location” field is hidden under the add-to-log button.
I am running Polo on a Google Pixel 9. I joined the beta program, so I should be able to test any beta builds for fixes.
Fortunately, I’m not really contesting with only five QSOs, just adding 1 to a few others stations’ totals, so I can still test editing my logs for those QSOs to add my own contest serial numbers.
Ah, I see. Yeah, when the screen is that small, and you enable an activity like VAQP that requires two extra fields, PoLo should be automatically hiding the RST fields.
I’ll add this to the list of things to fix.
In the meantime, you can hide those fields manually, using the “…” menu on the top right corner.
I hadn’t thought of hiding RST… If you hide them automatically, could you preferentially hide Sent? I heard a few real RSTs (not perfunctory 599) being sent in that QSO party.
Maybe use multiple rows to show all the fields when editing a QSO vs. a single line when entering a new QSO?
You can tap on the “More” button (with the pencil icon) on the secondary controls row (where time, frequency, p2p, etc are) and edit all the QSO fields there.
