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

Alias Edit Button appears wrong spot (was menu slider) #6822

Closed
baconpaul opened this issue Jan 25, 2023 · 7 comments · Fixed by #6865
Closed

Alias Edit Button appears wrong spot (was menu slider) #6822

baconpaul opened this issue Jan 25, 2023 · 7 comments · Fixed by #6865
Labels
Accessibility Issues related to making Surge more accessible Bug Report Item submitted using the Bug Report template
Milestone

Comments

@baconpaul
Copy link
Collaborator

Tab into the shape slider and arrow down/up to the aditive option. What happen, or doesn't I guess is the open editor button doesn't appear. Don't know if it's just a accessibility or also a visual thing but it's not reachable either with VO or shift+tabbing back

Reminder to self to check this

@baconpaul baconpaul added Bug Report Item submitted using the Bug Report template Accessibility Issues related to making Surge more accessible labels Jan 25, 2023
@baconpaul baconpaul added this to the Surge XT 1.2 milestone Jan 25, 2023
baconpaul added a commit to baconpaul/surge that referenced this issue Jan 25, 2023
Discrete (menu) sliders rebuild on menu change but not arrow
so do that. But rebuilding on every arrow is annoying in VO
so di it at the end.

Also invalidate a few other places

Addresses surge-synthesizer#6822
@mkruselj
Copy link
Collaborator

Visually it works fine it seems.

baconpaul added a commit that referenced this issue Jan 25, 2023
Discrete (menu) sliders rebuild on menu change but not arrow
so do that. But rebuilding on every arrow is annoying in VO
so di it at the end.

Also invalidate a few other places

Addresses #6822
@baconpaul
Copy link
Collaborator Author

Yeah I just did a push to make it closer to what the menu does which helps a lot

@baconpaul
Copy link
Collaborator Author

Confirmed the change above improves the reset-slider-name behavior. Not sure why the edit button is so hard to find when going additive though; maybe need to change a tab order?

@mkruselj
Copy link
Collaborator

mkruselj commented Feb 1, 2023

@baconpaul Can we close this one?

@baconpaul
Copy link
Collaborator Author

no i still need to find that edit button position in tab order. i'll rename it.

@baconpaul baconpaul changed the title Accessible menu as slider issue Alias Edit Button appears wrong spot (was menu slider) Feb 1, 2023
@baconpaul
Copy link
Collaborator Author

There are a couple of things that seem to work fine throughout Surge, except for in the additive editor which is part of alias. The first being the inability to hit right bracket to do a right-click (which is a cool feature BTW, not sure when that got added in but I discovered it by accident like a month ago). The second is that the button to invoke/dismiss the editor doesn't respond to the enter key.

I remember a pass was done to fix a lot of these types of enter key issues all over the place, but that must have been forgotten about.

@baconpaul
Copy link
Collaborator Author

Oh that’s a comment from bacross on discord

baconpaul added a commit to baconpaul/surge that referenced this issue Mar 3, 2023
1. The CustomEdit has the right "size" so it works in tab traversal
2. The Menu/Right Bracket callbacks all work
3. Enter on CustomEdit butto activated

Closes surge-synthesizer#6822
baconpaul added a commit that referenced this issue Mar 3, 2023
1. The CustomEdit has the right "size" so it works in tab traversal
2. The Menu/Right Bracket callbacks all work
3. Enter on CustomEdit butto activated

Closes #6822
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 Bug Report Item submitted using the Bug Report template
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants