Bug #11248
openChirp-Next - UI Issue
0%
Description
In Chirp-Next (CHIRP next-20240312 on Win32 (Unknown 10.0:19045) (Python 3.10.8)), in Settings, when a field is edited and the tab key is pressed,
the focus goes to the "Field Name", and subsequent tab key presses do not move the focus to the next field.
Instead, the tab key moves the focus to the tab with of Current File (Top most tab strip),
then to the "Settings" tab (tab strip containing "Memories" and "Settings" tabs),
then to the "Settings" list/tree containing on the Setting you are editing (on the left, "Work Mode Settings" for example),
then to the field label of the setting being edited,
then finally back to the value of the setting being edited.
For clarity:
Enter a value in "Power-On Message 1",
Pressing tab sets the focus to the top row of tabs to "Baofeng_BF-F8HP_20240314.img"
Pressing tab again sets the focus to the "Settings" tab of the "Memories"/"Settings" tab control
Pressing tab again sets the focus to the "Other Settings" in the "Settings" Tree/List control
Pressing tab again sets the focus to the "Power-On Message 1" label field
Pressing tab again sets the focus to the "Power-On Message 1" value field.
Typically in Windows applications, pressing the Tab key takes you to the next editable field.
Thanks,
Eric
No data to display