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

[MU4 Issue] Spin boxes won't accept keyboard input #13476

Open
rgreen5 opened this issue Sep 24, 2022 · 7 comments · May be fixed by #25016
Open

[MU4 Issue] Spin boxes won't accept keyboard input #13476

rgreen5 opened this issue Sep 24, 2022 · 7 comments · May be fixed by #25016
Labels
os: linux Potentially specific to Linux-based operating systems P2 Priority: Medium Qt-next Either broken or fixed by (updating to) newer Qt versions than we currently use

Comments

@rgreen5
Copy link

rgreen5 commented Sep 24, 2022

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

  1. Open the attached file.
    spin_box_issue.zip
  2. Click on a fingering and click on the "Appearance" button (Properties panel)
  3. Change the vertical offset by dragging or using the spin control
  4. Now try to enter 0 (zero) in the spin box.

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

@rgreen5 rgreen5 changed the title [MU4 Issue] Spin box won't allow keyboard input in certain cases [MU4 Issue] Spin box won't allow keyboard input Sep 27, 2022
@rgreen5 rgreen5 changed the title [MU4 Issue] Spin box won't allow keyboard input [MU4 Issue] Spin boxes won't allow keyboard input (all properties affected) Sep 27, 2022
@rgreen5 rgreen5 changed the title [MU4 Issue] Spin boxes won't allow keyboard input (all properties affected) [MU4 Issue] Spin boxes won't allow keyboard input Sep 27, 2022
@rgreen5 rgreen5 changed the title [MU4 Issue] Spin boxes won't allow keyboard input [MU4 Issue] Spin boxes won't accept keyboard input Sep 27, 2022
@rgreen5
Copy link
Author

rgreen5 commented Sep 27, 2022

This problem affects spin boxes of all properties. For example:

  1. Click on a notehead.
  2. Open Properties > General > "Playback".
  3. Click in the "Velocity" spin box.
    RESULT: Box accepts keyboard input, deleting, highlighting, editing etc.
  4. Now, with the same tab open click on another note
  5. Try to repeat step 3.
    RESULT: Cursor won't appear in spin box and no keyboard input is accepted.

@MarcSabatella
Copy link
Contributor

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.

@shoogle
Copy link
Contributor

shoogle commented Sep 30, 2022

I can't reproduce this on macOS. I'm running macOS 11.6.8 Big Sur on a MacBook Pro 2015 (Intel).

@rgreen5
Copy link
Author

rgreen5 commented Nov 7, 2022

Bump.

@oktophonie
Copy link
Contributor

I can reproduce this on Linux (and it's very, very annoying) but not on Windows; so it appears to be Linux-specific.

@sammik
Copy link
Contributor

sammik commented Dec 19, 2022

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.

@cbjeukendrup cbjeukendrup added the P2 Priority: Medium label Mar 4, 2023
@cbjeukendrup cbjeukendrup moved this to One of the next releases in MuseScore Studio Backlog May 19, 2024
@cbjeukendrup cbjeukendrup added the os: linux Potentially specific to Linux-based operating systems label Feb 28, 2025
@cbjeukendrup
Copy link
Contributor

Looks very similar to #25300, and as such probably fixed when we update to Qt 6.8.

@cbjeukendrup cbjeukendrup added the Qt-next Either broken or fixed by (updating to) newer Qt versions than we currently use label Feb 28, 2025
@cbjeukendrup cbjeukendrup linked a pull request Feb 28, 2025 that will close this issue
@cbjeukendrup cbjeukendrup moved this to In Progress in MuseScore Studio 4.6 Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
os: linux Potentially specific to Linux-based operating systems P2 Priority: Medium Qt-next Either broken or fixed by (updating to) newer Qt versions than we currently use
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

7 participants