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

Tab input shortcut no longer working #20688

Closed
Aztecslug opened this issue Dec 24, 2023 · 2 comments
Closed

Tab input shortcut no longer working #20688

Aztecslug opened this issue Dec 24, 2023 · 2 comments
Labels
needs info More information is required before action can be taken regression Regression on a prior release UX/interaction

Comments

@Aztecslug
Copy link

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

I'm a guitar teacher who uses Musescore to transcribe pieces and exercises for my students.

Yesterday when trying to write out an exercise I could no longer input fret numbers on my tab by using the number keys on my keyboard. Before the update to 4.2 I could just use 'shift' + number key (I'm on Mac) to input the fret number but this no longer works, and I have to manually use my 'up' key until I reach the desired fret.

There's no issue with my keyboard, as I can type in numbers on any other program including Musescore 3.

I tried restarting Musescore and my laptop but neither yielded a result.

I've uninstalled and reinstalled Musescore and that didn't help either.

The shortcuts haven't changed or been corrupted, they are listed identically to the shortcuts in Musescore 3 where Tab input works fine.

I've checked other forums and it seems like this isn't a common issue, but I can't efficiently use the program for my work and don't know what to do.

Steps to reproduce

None

Screenshots/Screen recordings

No response

MuseScore Version

4.2.0

Regression

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

Operating system

macOS Ventura (13.6.1°

Additional context

No response

@muse-bot muse-bot added regression Regression on a prior release UX/interaction labels Dec 24, 2023
@MarcSabatella
Copy link
Contributor

This works fine for me and other users, so there must be something unique/unusual about your system configuration that is getting in the way.

You say the tab shortcuts are listed the same as before,e but did you try redefining them? Also, do the letter keys still work? What happens if you do Help / Revert to factory settings?

Also, check to be sure no new programs have been installed recently that could be interfering with keyboard processing. Programs that implement macros are a common culprit that cause similar issues.

Also please ZIP and attach a specific score you are having trouble with and give precise steps to reproduce the problem. Could be the issue is related to the configuration of the staff itself. Even if this seems unlikely, since no one else can reproduce this, we need all the info we can to understand what might be going on.

@cbjeukendrup cbjeukendrup added the needs info More information is required before action can be taken label Dec 24, 2023
@bkunda
Copy link

bkunda commented Jan 16, 2024

Closing this for now due to inactivity. Happy to re-open if a genuine bug can be identified!

@bkunda bkunda closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info More information is required before action can be taken regression Regression on a prior release UX/interaction
Projects
None yet
Development

No branches or pull requests

5 participants