Change in behaviour of default selected after delete

• Apr 12, 2019 - 07:49

It's been an absolute joy discovering this amazing piece of software called MuseScore.
Now I'm trying to 'spread the word' to the music teachers my children have. Also contributing translating MuseScore to Danish.

Typically the music teachers are already comfortable using Sibelius - ultimately delegating the cost to the students. That's the competition MuseScore must beat.

In Sibelius deleting a slur automatically highlights the first note enabling creating a new slur from the same originating point easy. In MuseScore the slur is deleted. Subsequently in MuseScore the first note must be highlighted manually.
It's a little thing - but a time consuming one when editing a large piece.

In Sibelius the automatic highlight is normal behaviour resulting in a more efficient workload.
For example performance directions, dynamics, lines etc.

So my suggestion is, that default behaviour in these and other instances could be optimized.


Comments

It's already implemented in the 3.1 beta just released today.

Personally, I have mixed feelings about this. It doesn't seem quite right to me that after pressing Delete once, accidentally pressing it again might damage my score. But, I recognize there is value in this too, so I'm going with the flow.

Do you still have an unanswered question? Please log in first to post your question.