Specific keystrokes not allowed for shortcuts

• Dec 31, 2018 - 17:07

When I try to define custom shortcuts, there are certain keystrokes that are straight up not recognized, for example:

ctrl + tab, or ctrl + shift + tab (these are the standard for switching tabs in Chrome, it would be reasonable to use them for switching scores in MS since the reflex is consolidated already and reinforced daily).

shift + any arrow (moving throughout the score efficiently is crucial, and one needs different shortcuts for next chord, next measure, next voice, etc... so it's a shame to not be able to use the shift key for this purpose).

Comments

• Dec 31, 2018 - 20:09

They are assigned by default to add next or previous chord to selection and to add next or previous staff to selection. Since they are on the customizable list I figured I should be able to reassign them however I see fit.

But the problem is that even after removing these key combinations from those shortcuts, I'm not able to assign them to any others. More so, if I try to reassign them to the original actions, it still does not recognize the keystrokes when I enter them. That is, once you've cleared them, you can't redefine them back the way they came because MuseScore doesn't recognize shift + arrows when asking you to define your combinations.

Reply

• Dec 31, 2018 - 21:12

I managed to do that, there is a button to restore shortcuts to default individually. I still believe this should be reported though. If they are on that list they are supposed to be customizable. But it's not that big a deal, now that I know what these combinations CAN do, it is rather useful to be honest, so I don't really mind not being allowed to change that to something else.

Now, ctrl + tab is a whole different story. I can't get it to work no matter what. Is it just me?

Reply

Do you still have an unanswered question? Please log in first to post your question.