Deleting vs selection
Using v2 (1efc609), I am quite surprise by the selection policy when deleting.
1/ When I delete an embellishment among multiple embellishments, I expect at least the next or previous embellishment to be selected, but none is.
2/ When I delete a single embellishment I expect the note it is attached to to be selected but it's not.
3/ When I deleted a note I expect the silence to be selected , but nothing is selected.
4/ And so on for many note attributes/symbols.
I expect that beacause it is useful to move among notes with left/right arrows, but needs a selection.
Nothing selected implies a mouse click.
Or may be I don't understand what other advantage this behaviour gives.
Comments
It would help if you posted a sample score and described more exactly what you are trying to do. By "embellishment" do you mean the markings from the articulations palette etc? I guess having something else automatically be selected after a deletion might sometimes be useful, but in general, it's not what I'd expect. Other layout-oriented programs I use don't work that way.
In reply to It would help if you posted a by Marc Sabatella
Please take a look at the score in attachment, done just by choosing bagpipe instrument and bbb key signature (can anyone explain why I see only b key signature at the end ?).
Now the scenario :
1/ select the second bagpipe embellishment note (A) before the first real note of the score in measure 1.
2/ delete it
3/ nothing is anymore selected in the score, but you will surely do something else, maybe not what the program would select by default, but selecting nothing, you are sure to have to click somewhere before to do something and you can not use left and right arrow key to move.
4/ Same thing in mesure 2, if you delete first note or ">" over second note, nothing is selected.
I never used other editing score software before MuseScore, so I can't compare, but I use other kind of software and I got more an expectation of general software user than a musician software user, but I think than selecting nothing is not good and selecting something by default even if you don't use it can't be wrong.
Maybe...
In reply to Please take a look at the by madsenfr
Actually, I wasn't thinking of other music software but things like desktop publishing or drawing programs. Anything where you place objects on a page and position them. Most that I know of don't select anything after deleting. But come to think of it maybe they should. Especially considering all the work going into making MuseScore more keyboard accessible for the benefit of blinds users. So perhaps we'll end up doing something for that reason.
In reply to Actually, I wasn't thinking by Marc Sabatella
The suggestion did not seem sensible to me, and I'd suggest that any proposed implementation be optional via Preferences. Otherwise, a significant inconvenience would be created for the many users who do not wish something to be selected automatically - or who do not wish the software to second-guess their next move in any event.
In reply to The suggestion did not seem by [DELETED] 448831
I agree; *normal* behavior should be that after deleting something, nothing is selected. hitting delete twice in a row shouldn't result in multiple things being deleted. Doesn't work that way in any other programs (except of course text editors, but that's totally different) and it would be be surprising and disappointing here. Still, for accessibility sake, there will need to be some way to either prevent the selection from being lost, or an easy way to regain it (like simply hitting Enter). That's something we'll be sorting out as we get more accessibility features in.
In reply to I agree; *normal* behavior by Marc Sabatella
"Doesn't work that way in any other programs (except of course text editors, but that's totally different)"
Why is it totally different? In both cases you write something (mostly) sequentially, and you often want to delete sequentially as well. I think it might be an interesting idea, even for those of us who are not blind. On the other hand, some of this behavior is already there. When you delete something, something else is usually still selected, but the selection doesn't advance.
"I agree; *normal* behavior should be that after deleting something, nothing is selected. hitting delete twice in a row shouldn't result in multiple things being deleted."
For that there is ^z.
In reply to Why is it different? by RexC
Do you see the difference between a text editor and a desktop publishing or graphics program? A text editor is *primarily* about a string of charcaters that rearrange themselves as you go; you don't normally position each separately, although it might provide some sort of facility for that as well. A desktop publishing or graphics program is *primarily* about placing and positioning objects individually on a page, although it might provide some sort of text submode as well.
MuseScore is in almost all respects more like the latter than the former. So I think users familiar with both types of programs would be expecting more of the latter type of use model. While you arer in note input mode - the text-editing-like mode - sure, it makes sense for the cursor to remain present. but when you are not in note input mode, everything about MuseScore is much more like a desktop publishing or graphics program.