Accidentals entered by toolbar do not honour preceeding accidentals in measure

Hi

Thanks for your report.

What version and operating system are you using?

(edited)

This must is regarding 1.3, as the development builds behave differently - the second F inherits the sharp automatically, with no accidental added.

Assuming this report is indeed regarding 1.3, then, this isn't a bug. The toolbar / palette is *supposed* to be a no-questions-asked accidental, so you can do courtesy accidentals. That actually remains true in the development builds - applying a toolbar or palette accidental applies that accidental in all cases. It's just that it won't be needed in this case, because the second F will automatically inherit the sharp. But if you apply a natural and then a sharp, the sharp displays, just as it should. If you want MuseScore to figure out if an accidental is needed or not, don't use the toolbar or palette - use the arrows. The toolbar / palette is for when you definitely want to see an accidental. At least, that's my understanding.

True, but you're entering an accidental. You enter a quarter note, you get a quarter note. You enter a tie, you get a tie. You enter a sharp, you should get a sharp. At least, that seems natural to me (pun not intended). If the icon had a picture of an up arrow, then I'd understand it as raising the pitch and applying whatever accidental was required, but with a picture of a sharp, I expect it to apply a sharp, always.

And consider, what should happen if the key signature is, say, F major, so Bb is in the key signature, and you type B and then press the sharp sign? Up arrow would add a natural, not a sharp. But that would be entirely counterintuitive for an icon with a picture of a sharp on it. You'd probably expect pressing the icon to actually add a sharp. In other words, you'd want the toolbar icon to act like the palette in this case, So the toolbar icons would be acting like the arrow keys sometimes, like the palette at other times. Do we really need three different ways of doing things (palette behaves one way, arrows behave another, toolbar another still)?

It's largely unimportant, though, since as mentioned, this issue will hardly ever come up in 2.0. As soon as you press that second "F" in your example, you get an F#. That is, the note displays with no accidental and plays an F#. So you won't normally need to use the toolbar to enter that second F#. It would come up only in the scenario I describe: where you first entered it by typing F, thus yielding an F# with no accidental, then you used down arrow or the natural icon to lower the pitch.

This should probably be closed as "by design", but since this *is* a common source of confusion and there has already been change for 2.0 in this area and it's perhaps not too late to revisit how any of this works and in any event it's not my call to make, I'm leaving it open for now as a minor feature request.