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

Keyboard is not focused to value input when editing modulation values from context menu #5758

Open
xard-dev opened this issue Jan 12, 2022 · 9 comments
Labels
Bug Report Item submitted using the Bug Report template Linux Issues which only occur on Linux UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.

Comments

@xard-dev
Copy link

xard-dev commented Jan 12, 2022

Bug Description:
Keyboard is not focused to value input when editing modulation values from context menu and the field needs to be clicked before a value can be written.

Surge Version:

  • Version: Surge XT 0.99.nightly.320cd70
  • Plugin Type: VST3, LV2
  • Bitness: 64-bit

Reproduction Steps:

  1. Open control like Filter cutoff context menu
  2. Click on any modulation edit icons OR click Add modulation from context menu item adding a new modulation target
  3. Type value

Expected Behavior:
A value can be inserted directly.

Screenshots:
image

Computer Information (please complete the following information):

  • OS: Ubuntu 20.04
  • Host: Carla, Ardour
  • Version: 2.1.0, 6.9

Additional Information:
When opening context menu for a control and choosing Edit value the keyboard focus is in the popup field and the value can be inserted directly.

@xard-dev xard-dev added the Bug Report Item submitted using the Bug Report template label Jan 12, 2022
@baconpaul
Copy link
Collaborator

OK this isn't a problem on mac but i happen to be in linux now so let me look

@baconpaul
Copy link
Collaborator

oh and confirmed that on linux it does happen. and it is annoying.

@baconpaul
Copy link
Collaborator

hmm i have no idea how to fix this
it's super annoying but i don't think i would block on it. I thought it might be our custom focus handlers but it isn't.

Oh @xard-dev I'm also interested if that , as . works properly with the parsing?

@xard-dev
Copy link
Author

xard-dev commented Jan 12, 2022

For my regional settings decimal separator comma , works as expected but period . is ignored and the values after period are discarded.

@xard-dev
Copy link
Author

And If I temporarily change to LC_ALL=C the period . is used instead of comma , as expected.

@baconpaul
Copy link
Collaborator

great thanks!

@mkruselj mkruselj added the UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. label Jan 13, 2022
@j5v
Copy link
Contributor

j5v commented Jan 24, 2022

I came here to report this bug.
What might help: While the 'edit value' box is being displayed, I can right-click again and again select the edit icon in the context menu. If I can get the value to focus, then repeated attempts will always be in focus. However, if the 'edit value' box is not focused, then it might, or might not focus next time.
I suspect a race condition between display and focus.

@baconpaul
Copy link
Collaborator

Yeah it’s all single threaded but I wonder if I need a show message to get a cycle before the focus message. Excellent observation

@eigenvoid
Copy link

I have this bug too on Surge XT 1.3.4 on Arch Linux with KDE and X11. Right-clicking on a slider and choosing "Edit Value," the value box will not be focused, and you have to click it a few times to be able to edit it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template Linux Issues which only occur on Linux UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Development

No branches or pull requests

5 participants