Glissando type isn't properly replaced

• Feb 24, 2015 - 14:39
Type
Functional
Severity
3
Status
closed
Project
MuseScore

1. Create score.
2. Enable 'Note Entry'.
3. Enter one note, then another next to it.
4. Disable 'Note Entry'.
5. Click on first note.
6. Double-click straight glissando in palette.
7. Double-click wavy glissando in palette.

Result: Both are present.

8. 'Undo'.

Result: The straight glissando is present, but the distance between notes is shorter.

Note: Steps 6 and 7 can be reversed with a similar result.

Using MuseScore 2.0 Nightly Build 75018ae - Mac 10.7.5.

Comments

• Feb 24, 2015 - 18:41

For step 7: Unless, in the future, there is some special case behaviour (I'm not sure I know of one) in which glissandi fan out from one note (whether it's one, or both types), I suppose the straight glissando should be removed in the meantime.

Reply

• Feb 24, 2015 - 21:10

In other words, no more than one glissando per note.

Would it not be the case to simply ignore the attempt to drop another glissando on a note which already is the starting point of an existing glissando? If the user wants to change the glissando type, he can do exactly that on the existing glissando, can't he?

Reply

• Feb 24, 2015 - 22:22

I don't understand your final sentence.

I think what you are suggesting above that is making it not possible to add a glissando where one exists already? Instead, you would remove the existing one and then add the other.

Reply

• Feb 25, 2015 - 02:44

I think he's suggesting you simply change the existing glissando using the inspector. That would be the normal way of doing what I asusme you are trying to do here - changing from straight to wavy or vice versa.

Reply

• Feb 25, 2015 - 08:50

Marc got my point indeed!

Your proposal: if the user tries to attach a new glissando to a note which already starts one, the programme should remove the existing glissando and insert a new one in its stead.

My counter-proposal: if the user...., the programme should simply ignore the new glissando, keeping the old one. If the reason for replacing the existing one is to change some of its properties, the currently supported way should be to do exactly this: change the properties of the existing glissando (via the Inspector or whatever).

In any case, 'fanning' several glissandi out of a single note is not supported (and it will not for 2.0).

Did I explain myself more clearly?

Reply