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

Can't input natural accidental with Portuguese keyboard #24968

Open
4 tasks done
goncalogato opened this issue Sep 29, 2024 · 4 comments
Open
4 tasks done

Can't input natural accidental with Portuguese keyboard #24968

goncalogato opened this issue Sep 29, 2024 · 4 comments

Comments

@goncalogato
Copy link

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Can't use the keyboard to input a natural sign for a pitch. I think it's because of the Portuguese keyboard layout. I have to use the combination Shift-0 to get the '=' sign which translates to the natural accidental. Thanks!

Supporting files, videos and screenshots

No files needed.

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

4.4.2

Regression

I was unable to check

Operating system

MacOS Sequoia

Additional context

No response

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
@goncalogato
Copy link
Author

goncalogato commented Sep 29, 2024

...And '0' is used for rests. So I defined a keyboard shortcut using another key which has no conflicts.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Sep 29, 2024

Same issue with a German keyboard, here too = is Shift+0

@FrancRos31
Copy link

Same for italian , I reported it in #24951.

@Jojo-Schmitz
Copy link
Contributor

Different issue, most probably same cause

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants