When using smart pen / touch screen input, on Windows 11, some on-screen function buttons become unable to be used through any input method.

UncleRed0899 commented 2 weeks ago

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Open MuseScore Score (Any Score. Untitled, pre-saved, "edit on desktop" from Musescore.com Public Score etc...
Using a smart-pen input on device using Windows 11 (Windows ink) Wacom AES Protocol input, attempt to use Musescore normally, especially using playback Play/Pause, Toolbar relocation bar, Rewind, and/or attempt to change score tempo or bar/beat location
Watch for the on-screen action button to become "greyed" or become stuck in the color of the icon when it is normally moused over with the mouse cursor when using normal mouse/trackpad input.
Attempt to use the "greyed-out" action button via pen input, mouse input, or keyboard input
Button becomes inoperative and stays inoperative unless user navigates to the "View" tab, disables, then enables the toolbar's UI visibility.
The button will be operative again.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/3883ebba-fe80-46c0-8fc7-3645cabf648e

I apologize for the sped up video, and very brief representation of this issue. Tried to conform to the "Ideally 20s or less" rule, here. This should show it well enough, however.

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00

Regression

I was unable to check

Operating system

Windows 11 Home

Additional context

Device: Lenovo Ideapad Flex 5i 2-in-1 laptop Pen Protocol: Wacom AES 3.0 Smart Pen Used: Wacom Bamboo Ink Plus (This isn't pen specific, but in case you all would have liked to know...)

Checklist

[X] This report follows the guidelines for reporting bugs and issues
[X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
[X] I have attached all requested files and information to this report
[X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

bkunda commented 1 week ago

Has this always worked for you (using previous versions)? We don't officially support touch screen interactions, so addressing this will likely fall in the realm of a feature request.

UncleRed0899 commented 1 week ago

No, I've only recently began attempting to use my smart pen to edit a score. I wasn't aware that touch interaction wasn't within the scope of its everyday use, since so many devices now are either 2-in-1 or tablets that can also download, install, and run Musescore. I simply assumed it was within the scope for you-all. I apologize if I submitted this to the wrong thread.

cbjeukendrup commented 1 week ago

From a technical point of view, I'm not sure if MuseScore would actually be able to distinguish between mouse and touch interactions at all; more likely, this is fully handled by Qt, so there is a chance that this is caused by a Qt bug. Have you ever seen similar behaviour in other apps?

To ensure we understand the problem correctly: when you tap the "Rewind" button, it becomes highlighted and stays highlighted but isn't functional anymore, even when you move the mouse/pen to somewhere else. Is that right? And does it only happen with the "Rewind" button, or can it happen to any button? How reliable is it, does it happen always or only unpredictably?

(Also, the fact that the entire playback toolbar becomes invisible at some point in the video is because you undock it and/or hide it via the View menu, right? The View menu is namely not visible in the video (only the main window), which was initially confusing.)

UncleRed0899 commented 6 days ago

Yes, I'm sorry. i should've clarified what I did to "fix" it. I have to Undock/Dock the playback tool panel for it to be resolved, which is why it "disappeared" momentarily. I just undocked it and redocked it in that exact moment. (Github only allows for 5MB uploads so I had to increase the speed of the video, and shorten it as much as possible so that it could be uploaded. I apologize for the lack of detail, as it was originally recorded with more than what's currently shown)

At times though, the "Move" button for changing its position on the screen becomes highlighted, and stays highlighted, preventing mouse OR pen input, just as the rewind button did as shown in the video.

But you are correct, that is exactly what happens. The Rewind button (or any button on the panel, for that matter) becomes highlighted and stays highlighted as if the cursor is on top of the button, and once it does this, the action is not able to be access via mouse, pen or touch input. And it is a reliably recreate-able problem, as far as I've noticed from goofing around with it.

UncleRed0899 commented 6 days ago

Also, apologies on the late response. Have been busy, as of late.

cbjeukendrup commented 6 days ago

No worries!

Most likely this can only be fixed by moving to a new version of Qt, assuming that it is indeed a Qt bug and they fixed it in a later version. There's a slim chance that #24644 already fixes it; you could give that build a try (see How to download test builds from pull requests).

musescore / MuseScore