-
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
[MU4 Issue] Spin boxes won't accept keyboard input #13476
Comments
This problem affects spin boxes of all properties. For example:
|
I can confirm this on Linux, basically the spin boxes work only once per session with the properties window. Typing doesn't work until you clear the selection or close the Appearance button. As long as the Appearance window remains open, I can't type into it after the first note. Windows seems better. |
I can't reproduce this on macOS. I'm running macOS 11.6.8 Big Sur on a MacBook Pro 2015 (Intel). |
Bump. |
I can reproduce this on Linux (and it's very, very annoying) but not on Windows; so it appears to be Linux-specific. |
I can confirm on Linux. And it is more general problem with Playback / Appearance popup. If user clicks element first and then Playback, or Apearence in Properties, spin boxes do accept keyboard input. But if Appearance, or Playback is already open and user than click new element (note, or fingering, or whatever), spin box is not accesible. |
Looks very similar to #25300, and as such probably fixed when we update to Qt 6.8. |
Describe the bug
If you change the offset of an object, you should be able to reset it by entering a 0 (zero) from the keyboard in the relevant spin box. However the spin box will not accept keyboard input.
To Reproduce
spin_box_issue.zip
RESULT: The box won't accept keyboard input. Curiously, if you drag the fingering without opening the "Appearance" section, the spin box does accept keyboard input.
Expected behavior
Keyboard input to a spin box should always be accepted.
Platform information
OS: Linux Mint 20.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-3117031689, revision: github-musescore-musescore-bd3e1bb
The text was updated successfully, but these errors were encountered: