Editing a call sign (still a bug)

[KZ3L]

I’m reiterating this here because it’s still a problem in 0.11.4. Is this still in the list to fix?

Like the original poster mentioned, entering a call sign suffix and then inserting the prefix is problematic.

My most recent thread:

Callsign Edit Problem (still a problem)

Is this still in the queue?

Original thread:

Callsign edit problem

I came across a bug last night while activating a POTA park. Say I caught the suffix of a call so I go back to add the prefix, the first letter will go where I want then the cursor will jump to the end of the call and the rest of what I type goes in the wrong place. Not a huge issue once I figured out what was going on but could be a little smoother. I’m on Version 0.11.0, iPad OS 14.5, first gen iPad Pro 12.9" with smart keyboard. -Jake KF0ARE

[Jarrett]

It’s a priority yes. I can’t find the hook in iOS that seems to be doing this. I also find it very, very annoying in the field!

[KZ3L]

Thanks, @jarrett. It clearly has something to do with your formatting function – the method you’re using to ensure all caps, or in the case of grid squares, to format uppercase/lowercase. This happens in all Callsign fields and in the grid square entry, but not in the Comments field (which uses no validation).

Perhaps there is an alternate way to reformat an entry in these fields?

[K0LAF]

Amazon Fire tablet has the same issue.