Actually here something strange happens. If after opening a score, deleting a frame and undoing it start a note input and enter some note, the frame appears back. Still if I enter some notes first, delete a frame and start to undo all those actions, then the frame seems to appear but after a wrong number of undo commands.
After adding any other element, we setLayout at the element's
location. However, for boxes, there is an early return, and this step is
missed, meaning the box won't appear until a relevant measure is layed out.
This fix adds the missing setLayout._
Comments
In fact, this bug applies to all frames.
I thought all similar issues were resolved already :(
#283545: Crash on undoing removal horizontal frame
#285888: Crash on removing a horizontal frame twice
Actually here something strange happens. If after opening a score, deleting a frame and undoing it start a note input and enter some note, the frame appears back. Still if I enter some notes first, delete a frame and start to undo all those actions, then the frame seems to appear but after a wrong number of undo commands.
Anyway, yes, that should be fixed.
I'll see if I can take a look at this.
https://github.com/musescore/MuseScore/pull/5293
Fixed in branch master, commit 3f40a56dd9
_fix #293707: undo doesn't restore deleted frame immediately
Why do these changes fix this particular issue?
After adding any other element, we
setLayoutat the element'slocation. However, for boxes, there is an early return, and this step is
missed, meaning the box won't appear until a relevant measure is layed out.
This fix adds the missing
setLayout._Fixed in branch master, commit 60f463f7fb
_Merge pull request #5293 from jthistle/293707-undo-no-restore-deleted-frame
fix #293707: undo doesn't restore deleted frame immediately_
Automatically closed -- issue fixed for 2 weeks with no activity.