Glissando not always drawn after dragging it

• Feb 27, 2015 - 23:55
S4 - Minor

1. Open attached score (produced in 1.3).
2. Drag glissando away from stave (using mouse).
3. 'Edit'>'Undo' (I did it via shortcut).
4. Click page.

Result: The glissando disappears.


It may not always be reproducible - if the case, click somewhere on the page and try again.
It will reappear after an action (e.g. 'Select All').
It is also reproducible in a 2.0 score.
After reproducing and it reappearing, it doesn't always seem possible to move it (either the bar will be selected, or the gliss, which doesn't move).

Using MuseScore 2.0 Nightly Build 561cae3 - Mac 10.7.5.


Status (old) fixed active

I can still reproduce this (being able to drag, not drawn after undo and clicking, unable to select etc).

Using MuseScore 2.0 Nightly Build f59e1af - Mac 10.7.5.

Status (old) active needs info

Well, I cannot reproduce with commit e492636 of today 16:24. I tried several times on the OP score and I could not notice anything wrong.

Dragging of glissando segments has been enabled and taken care of; as far as I can say here, it works.

Status (old) needs info active

I can drag just fine, and undo returns the gliss to its proper place just fine. Sometimes there is a slight bit of "trail" left behind in the old location - we aren't redrawing quite a large enough area of the score. But immediately after the undo, I cannot select the gliss - not until another layout operation (eg, Ctrl+A). That much is always reproducible for me. To be precise:

1) my first sacore, or any empty score with four measure on first system
2) enter two half notes in first measure
3) add gliss to first
4) drag away - note some trails exist
5) when done dragging press Ctrl+Z to undo - note some trail may be left behind here too
6) try to select gliss

Result: it can't be selected until you do something to force a relayout.

I still cannot reproduce: no matter I drag the glissando and undo, it is always still visible and selectable.

(I agree for the trails left behind; but they are purely visual and get erased at some next operation; I'm going to ignore this details, for the moment; it is due to the fact that the bounding box of the rotated text is hard to get).

Severity S4 - Minor
Status active fixed
Regression No
Workaround No

As nobody apart from the reporter seemed to be able to reproduce, and also there was a PR referenced that seems related to this, closing issue as "fixed".

@chen lung if you find this issue still persists, just reopen. Also i realized you opened a dozen of other issues regarding undo ~5 yrs ago, all collected now in #303762: [EPIC] Collection of Undo issues - you could help the community a lot if you kindly re-checked if all of these still persists in 3.4.2 or otherwise close them as "fixed".