It somehow found its way into one of the later MuseScore versions, but as mentiond, I believe it had been removed (or not done at all) from/for MuseScore 3, and on purpose.
Hiding rests using delete only happened in either 2.2 or 2.3, most of 2.x didn't allow using del to hide rests in voice 1. It was a bad experiment in my opinion.
Prior to MuseScore 2.2, attempting to delete a rest in voice 1 never used to have any effect at all. In MuseScore 3, when a user deletes a rest (in voice 2-4), the rest's gap property is set to true, and the rest is hidden from view. In MuseScore 2, rests did not have this gap property, and the deletion of a rest resulted in an actual gap in the score. This caused problems, especially when it came to gaps within tuplets. To solve this problem, we decided to prevent the deletion of rests. Making the rest invisible was our way of saying "you can't delete it, but we'll hide it for you." This was done for voice 1 rests as well as rests in voices 2-4. If we want this in MuseScore 3 (and it seems like maybe we don't) then it should only be done for voice 1 rests, since voice 2-4 rests are handled in their own way.
I also vote for leave it away and not re-implement it. I remember on several forum discussions, where people were confused about this feature. In my opinion it should be reserved for "v" to make elements invisible.
Comments
Hasn't that been done on purpose?
Workaround being the shortcur V or the corresponding "Visible" checkbox in Inspector
The intended use of the key is to delete things, right? If so, I don't think it should hide rests.
It somehow found its way into one of the later MuseScore versions, but as mentiond, I believe it had been removed (or not done at all) from/for MuseScore 3, and on purpose.
Hiding rests using delete only happened in either 2.2 or 2.3, most of 2.x didn't allow using del to hide rests in voice 1. It was a bad experiment in my opinion.
I was never a fan of this "feature" and would be happy to see it stay gone.
Prior to MuseScore 2.2, attempting to delete a rest in voice 1 never used to have any effect at all. In MuseScore 3, when a user deletes a rest (in voice 2-4), the rest's gap property is set to true, and the rest is hidden from view. In MuseScore 2, rests did not have this gap property, and the deletion of a rest resulted in an actual gap in the score. This caused problems, especially when it came to gaps within tuplets. To solve this problem, we decided to prevent the deletion of rests. Making the rest invisible was our way of saying "you can't delete it, but we'll hide it for you." This was done for voice 1 rests as well as rests in voices 2-4. If we want this in MuseScore 3 (and it seems like maybe we don't) then it should only be done for voice 1 rests, since voice 2-4 rests are handled in their own way.
I also vote for leave it away and not re-implement it. I remember on several forum discussions, where people were confused about this feature. In my opinion it should be reserved for "v" to make elements invisible.