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

4.2.1 - Keyboard Shortcut Issue on AZERTY Keyboards #22394

Closed
Jetinho opened this issue Apr 14, 2024 · 4 comments · Fixed by #22920
Closed

4.2.1 - Keyboard Shortcut Issue on AZERTY Keyboards #22394

Jetinho opened this issue Apr 14, 2024 · 4 comments · Fixed by #22920
Assignees
Labels
P1 Priority: High regression MS4 Regression on a prior release UX/interaction

Comments

@Jetinho
Copy link

Jetinho commented Apr 14, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

Bug Report: MuseScore 4.2.1 - Keyboard Shortcut Issue on AZERTY Keyboards

Summary: Users with AZERTY keyboards are experiencing a critical issue in MuseScore 4.2.1 where keyboard shortcuts used to change note durations (Shift + number keys) are non-functional. This problem, reported across various operating systems, particularly affects Mac users without numeric keypads. The shortcuts worked correctly in previous version 4.2.0, indicating a regression in the latest update.

Steps to Reproduce:

Impact: This bug severely affects usability for users relying on keyboard shortcuts for efficient score editing.

For more details, refer to the user discussion here. and here in english

Steps to reproduce

Use an AZERTY keyboard.
Attempt to change note durations using Shift + number keys.
Expected Result: The note duration changes as per the input.
Actual Result: No change in note duration occurs.

Screenshots/Screen recordings

No response

MuseScore Version

4.2.1

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

macOS

Additional context

No response

@muse-bot muse-bot added regression MS4 Regression on a prior release UX/interaction labels Apr 14, 2024
@bkunda bkunda added the P1 Priority: High label Apr 16, 2024
Eism added a commit to Eism/MuseScore that referenced this issue May 20, 2024
@zacjansheski
Copy link
Contributor

@Jetinho
could you confirm if #22906 resolves this issue?

RomanPudashkin added a commit that referenced this issue May 21, 2024
fixed #22394: Keyboard Shortcut Issue on AZERTY Keyboards
@RomanPudashkin RomanPudashkin closed this as completed by moving to Needs porting in MuseScore Studio 4.3.1 May 21, 2024
Eism added a commit to Eism/MuseScore that referenced this issue May 21, 2024
Eism added a commit that referenced this issue May 21, 2024
…_master

fixed #22394: Keyboard Shortcut Issue on AZERTY Keyboards. Master
@Jetinho
Copy link
Author

Jetinho commented May 21, 2024

@Jetinho could you confirm if #22906 resolves this issue?

Hi @zacjansheski, I don't know how I can test it.
Is there a wiki where I can find the information about how to run a local version of musescore directly from the repo ?

I could be interested in contributing to the project after learning the basics of the environment.

@oktophonie
Copy link
Contributor

@Jetinho There is indeed a guide here.

@Jetinho
Copy link
Author

Jetinho commented May 21, 2024

Thanks @oktophonie and @zacjansheski, I just checked and the problem is solved indeed 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority: High regression MS4 Regression on a prior release UX/interaction
Projects
Development

Successfully merging a pull request may close this issue.

7 participants