Skip to content

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

@UncleRed0899

Description

@UncleRed0899

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Open MuseScore Score (Any Score. Untitled, pre-saved, "edit on desktop" from Musescore.com Public Score etc...
  2. 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
  3. 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.
  4. Attempt to use the "greyed-out" action button via pen input, mouse input, or keyboard input
  5. Button becomes inoperative and stays inoperative unless user navigates to the "View" tab, disables, then enables the toolbar's UI visibility.
  6. The button will be operative again.

Supporting files, videos and screenshots

bug.recreation.mp4

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

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    UX/interactioncommunityIssues particularly suitable for community contributors to work onhelp wantedRequires specialist tools/skills that we don't haveneeds reviewThe issue needs review to set priority, fix version or change status etc.

    Type

    Projects

    Status

    Done

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions