-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tab between fields in Project Properties #27498
Comments
Use the Up/Down keys to navigate. MuseScore uses a hierarchical navigation model where Tab moves between groups of controls, Up/Down moves within them. |
Also relevant: #12851 @MarcSabatella's right that this is currently by design, however I think there's definitely a case to be made for some dialogs in MSS to be an exception to this design – especially where users are more likely to expect that TAB will move to the next field (rather than the next element in the upper-level of the hierarchy). |
My 2 cents: this keeps coming up over and over again by users who are used to the TAB key for years, myself included. And it is not a mild inconvenience. You guys (@MarcSabatella , @bkunda, @shoogle) admit in every discussion that the current system has flaws and they are obvious: getting stuck in edit controls and spin boxes as well as users not being used to using the arrow keys for navigation (and not wanting to change years-long habits). "Exceptions are needed" but are undesirable and will feel weird. Agree with all three. So I am wondering can't we have the best of both worlds: TAB key always navigates to the next field even if it is in the next panel and section. And arrow keys work the way they work now. So if I am a stubborn old-fashioned user, I'll use TAB even if this means 28948934 clicks, it's my problem. At the same time I have the option to press an arrow key to navigate if by any chance I want to. And whoever likes the new system with the arrow keys, can navigate with them (with the added bonus of having the option to resort to the TAB key to get out of the edit controls, LOL). If a TAB-lover wants to jump further than one control for faster navigation, they could use additional shortcuts like F6/Shift+F6 to the start of the desired group of controls and then continue with TAB to the target control. The current TAB function could be associated with another shortcut. On the other hand, if an ARROW-lover would be annoyed by not being able to use the TAB key as it works now, this could easily be made into an advanced setting, i.e. whether the TAB key navigates one control or an entire panel. IMHO MuseScore can benefit from more settings for better customization that suits way more users and tastes. There isn't a "one size that fits all". |
Besides, using the arrow keys to navigate means you get stuck in the 'copyright' tab and can't escape it. |
Confirmed regarding copyright - that much is a bug, then. |
Your idea
The project properties dialog box should allow going down through fields with the tab key, and up with shift-tab.
Problem to be solved
Currently, one must click in each project properties field to enter/change/remove text. Expected behavior would be to use the tab key to move between these fields.
Prior art
No response
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: