Enter e
Enter the sign for Sharp either by double-clicking on the sign in the Accidentals palette or by keyboard shortcut (I have # set for Sharp, ' set for flat, = for Natural).
You could also achieve this by entering e, pressing the UpArrow and then j a couple of times as j is the keyboard shortcut to change enharmonic "spelling" of a note.
I observe that e sharp is produced the "normal" way (i.e. up arrow on e natural) if the key signature is one that has a plausible cause for e sharp (such as a three-sharp-signature for e.g. f sharp minor). Similar for analogous cases like b sharp, c flat etc.
I believe this is a new feature in MS2; I never observed this when working with MS1. Really neat, could not be done better.
Glad you like it! I seem to recall there was actually a lot of tweaking of how that worked between 1.3 and 2.0. It's impossible to guess exactly what is wanted all the time, but the current algorithm is the result of a series of suggestions and compromises between conflicting requests and I agree it basically works well.
Comments
Enter e
Enter the sign for Sharp either by double-clicking on the sign in the Accidentals palette or by keyboard shortcut (I have # set for Sharp, ' set for flat, = for Natural).
You could also achieve this by entering e, pressing the UpArrow and then j a couple of times as j is the keyboard shortcut to change enharmonic "spelling" of a note.
https://musescore.org/en/handbook/accidental
You can use key [J] for enharmonic exchange. Or the button [#] in the note-entry-commandbar.
In reply to You can use key [J] for by KHS
I observe that e sharp is produced the "normal" way (i.e. up arrow on e natural) if the key signature is one that has a plausible cause for e sharp (such as a three-sharp-signature for e.g. f sharp minor). Similar for analogous cases like b sharp, c flat etc.
I believe this is a new feature in MS2; I never observed this when working with MS1. Really neat, could not be done better.
In reply to I observe that e sharp is by azumbrunn
Glad you like it! I seem to recall there was actually a lot of tweaking of how that worked between 1.3 and 2.0. It's impossible to guess exactly what is wanted all the time, but the current algorithm is the result of a series of suggestions and compromises between conflicting requests and I agree it basically works well.