Courtesy accidental doesn't disappear upon moving note
1. Create score.
2. Add C.
2. Add courtesy sharp to note.
3. Add another courtesy sharp to note.
3. Click on note.
4. Move it up or down.
Expected result: Accidental disappears and note moves normally.
Actual result: Note changes aurally, but visually retains a sharp when moving anywhere.
Using MuseScore 2.0 Nightly Build (4367) - Mac 10.6.7.
Comments
Here's the correct steps:
1. Create D major score.
2. Add C sharp note (not accidental).
3. Add courtesy sharp to note.
4. Click on note.
5. Move it anywhere.
The behaviour is a little different now.
There is still an accidental (sharps for Cs and Fs, naturals for anything else).
Using MuseScore 2.0 Nightly Build (bd8b902) - Mac 10.7.5.
I'm not sure if the current behaviour should be considered a bug. It looks like a question of design to me: Should MuseScore (ever) automatically delete (any) user created object?
In this special case: How would MuseScore know if a courtesy accidental is still needed/wanted after the note has been moved?
I'd vote for this: Anything the user creates explicitly (step 3) stays till the user deletes it.
Would there be negative side effects resulting from this policy?
I don't see how that makes sense. Key of D, a courtesy accidental on F#. Hit up arrow, which is defined to raise pitch a half step. There is no way to raise the pitch of F# a half step and keep the sharp. The new pitch could be spelled G, G natural, F double sharp, or A double flat, but there is no way to spell it with a sharp. I think pretty clearly MuseScore should not be choosing F double sharp or A double flat - it's got to be a G. The only question is whether an explicit accidental is retained - a natural in this case. I could go either way on that. I rather like that I can clear courtesy accidentals with arrow up/down right now (1.3). But sometimes I do wish they were retained.
Pressing UP on an F# (or dragging it to the G line) in D maj key signature both leads to a G nat for eee9f5f here, so I'm not sure I understand your point, Marc.
However:
- pressing UP/DOWN keys does not keep the courtesy accidental.
- dragging the note with the mouse does keep (a correctly adjusted) courtesy accidental.
So, currently there's some kind of inconsistency.
I took your previous suggestion literally: anything the user creates explicitly stays till the user deletes it. I assume you meant, the user created a sharp, so a sharp must remain at all times until deleted. Which doesn't make sense to me. So apparently you meant something else, but I can't tell what. Did you mean "some sort of visible symbol" must remain? Seems to me that's what chen lung is saying happens in the build he used.
I thought of a more general meaning of "object".
In this case: If the user specifies, that a note should have a courtesy accidental, then this note should always have such an accidental until the user deletes it. The "object" I was thinking of was "courtesy accidental", not "a sharp".
OK. In which case, indeed, it's a question of policy. I could see arguments both ways (accidental should stay until deleted / accidental should go because the pitch to which it applied no long exists).
But the original problem report described an actual bug where the sharp remained attached to the note. It appears that bug is fixed - probably long ago. And hence this issue should either be closed or at least renamed.
But I'm curious about response #2. The behavior described there would be consistent with the "accidental should stay until deleted" policy. But I can't reproduce that behavior. I get the same behavior as in 1.X - accidental disappears as soon as you hit an arrow key. Is there more to these steps than meets the eye? How is the note being added? How is the accidental being added?
See my #5: Don't use UP/DOWN keys but use the mouse to drag the note to get the behaviour described in #2.