Skip to content
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

Pre-select menu location in patch browser based on last selection (or at least on current category) #6832

Closed
baconpaul opened this issue Feb 3, 2023 · 5 comments
Labels
Accessibility Issues related to making Surge more accessible Feature Request New feature request
Milestone

Comments

@baconpaul
Copy link
Collaborator

SkycladSound — Yesterday at 5:25 AM

On another subject, sorry if this has come up before but, when dealing with tree views such as the patch browser tree view and the configuration tree, is there any way to make the cursor retain its position after an option has been selected? In this way, once a patch has been selected, you could carry on your keyboard browsing from that point and when, for example, making changes to the workflow menu to optimise accessibility, you would have to keep renavigating the tree again.

baconpaul — Today at 8:03 AM

There is PopupMenu::Options:::withInitiallySelectedItem (int idOfItemToBeSelected) const; which we might be able to use. Let me open an issue. But i don't think it will be easy since we have to remember. But we already remember with checkmarks so maybe it would be. Won't tackle today but will toss an issue into the 12 milestone to at leST look

@baconpaul baconpaul added Feature Request New feature request Accessibility Issues related to making Surge more accessible labels Feb 3, 2023
@baconpaul baconpaul added this to the Surge XT 1.2 milestone Feb 3, 2023
@mkruselj
Copy link
Collaborator

mkruselj commented Feb 3, 2023

I'm not sure that one will help us with submenus tho?

@baconpaul
Copy link
Collaborator Author

No but it does mean the patch browser could set initial focus on the category you have at least. Which could save 10s and 10s of screen reads

@mkruselj
Copy link
Collaborator

mkruselj commented Feb 3, 2023

Ah that is definitely true! Even as sighted I would appreciate this for keyboard navigation through menus.

@Alexander-Zyurkalov
Copy link
Contributor

looking

@Andreya-Autumn
Copy link
Collaborator

Completed, thanks and welcome Alexander!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Issues related to making Surge more accessible Feature Request New feature request
Projects
None yet
Development

No branches or pull requests

4 participants