[Reinhold H.]

David,

I analyzed the file. The issue is that 9 Pizz. sound changes in measure 72 are on top of each other. The order of the sound changes is that the selected one is the lowest in the list and is being overridden immediately by the next one. Because the next one is not selected it appears that the sound change still exist and is not selected. You can verify that by doing the steps (1)+(2) 8 times:
(1) select the sound change (stays black but the type is correctly displayed in yellow)
(2) delete it with the delete key
Afterwards the 9th selection highlights the last sound change symbol correctly. Or just select one and change the name.

From this behaviour there are actually 2 issues that I see:
(a) how can a second sound change being created on top of a former one at the same position? I had no luck to create this. Question to you: How were the sound changes created on top of each other?
(b) in case there are multiple sound change being created on top of each other for whatever reason, the currently selected one should be displayed in blue first and not being overritten by the next one. So far so good. But when this selected one is deleted, the next one is being displayed next in black. For the user this appears to be that deleting a selected sound change does not work.

This behaviour goes back to Composer 2.5.2 (the oldest that I have) and exists for more than 10 years now.

I checked the effort to implement (b). The effort is significant. I would therefore address (a) because it really helps where (b) just corrects something from the past but still confuses the user.

For (a) do you have any idea how those 9 sound changes on top of each other have been created?

All in all, this issue exists for a very long time now and therefore I see it to be a low priority in particular because I was not able to add soundchanges on top of each other. I will not hold back 3.0.7 because of this behaviour. But, of course, many thanks for reporting it. It is stored our TaskDB.

Reinhold