Chord symbol entry ruined (move to next measure)
I am trying to enter chord symbols and move to the next measure, as I have done for years. Now the manual says "Move cursor to next measure" is Cmd -> on mac.
Ruined my highest productivity feature by 1) making me press Enter, 2) making it two keys, and 2) and it doesn't work, it puts the Chord symbol into edit mode.
Unusable
Am I missing something?
Comments
Why you do need to press Enter? On my windows system, I can just type the desired Chord symbol and press CTRL+ -> to move to the next measure.
I can't fix the two keys....though you might be able to assign a different short cut.
In reply to Why you do need to press… by Henk De Groot
That would be ok if it worked on Mac OS. It doesn't, It only moves the chord symbol a typing character to the right.
In reply to That would be ok if it… by thrashjazz
On Mac keyboards, substitute “Cmd” any time we say “Ctrl”. But also see my other post about nightly builds and hover text.
The shortcut is Ctrl+Right (Cnd+Right on Mac keyboards), no Enter involved. This is consistent with the next measure shortcut in all other modes, designed to mimic how this same shortcut is next word in any text editor. Not sure what you mean about putting it into edit mode either - chords are already in edit mode while typing them.
In reply to The shortcut is Ctrl+Right … by Marc Sabatella
Chord SYMBOL entry, not CHORD.
In reply to Chord SYMBOL entry, not… by thrashjazz
Yes, that’s what I mean. Make sure you don’t leave edit mode by pressing zest. Right after typing the chord symbol, while the cursor is still blinking at the end of the text, press Cmd+Right.
There have been a handful of reports of certain Mag keyboards not working correctly with this. If yours is one of thise, please try a nightly build via the Download menu above to see if that works better. The processing of Ctrl/Cmd has been updated in ways that should work with more keyboards.
Also make sure you don’t have the “hover text” option enabled in macOS - this is known to cause some problems with the Cmd key in apps that use the Qt libraries as MuseScore does.