There’s been a number of complaints about the jumping cursor on the PC, where one enters a part of the callsign, say the suffix, then goes back to the beginning to enter the prefix only to have the cursor jump to the end of the callsign after typing a character. Using N8HC as an example, typing “HC” then going back to type “N8” results in “NHC8” being entered.
While on an activation today I noticed I wasn’t seeing this when my caps lock was turned on. I could cursor back to the start of the callsign and start typing and it would respond as it should, without jumping to the end after typing the first character. When turning the caps lock off it would go back to jumping. This is on a Windows 10 system.
I’d be curious to see if others find this to work for them as well.
–Glenn