8c2401f Crashes on "Undo" - crtl+x
1. Score with more than 1 part
2. Select top staff, Rt. click >Staff properties select small staff.
3. Save.
4. Using Styles, change distance between staves.
5. Undo more than once.
Result = crash.
1. Score with more than 1 part
2. Select top staff, Rt. click >Staff properties select small staff.
3. Save.
4. Using Styles, change distance between staves.
5. Undo more than once.
Result = crash.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Hi
I can't reproduce this.
Can you provide more precise steps, or a screencast?
BTW, stuff like this should probably be in the Technology Preview section.
Could also be dependent on the specific score involved - would help to post that.
BTW, probably just a typo, but just to be sure: Ctrl+X is cut, not Undo is Ctrl+Z. I tried both but couldn't get a crash.
In reply to Could also be dependent on by Marc Sabatella
Ctrl+Z.
It requires one to undo a few times.
It looks to me as if I do a couple of operations, save, do a couple/few more, then undo numerous times, trying to get it all back.
The part loaded was originally from 1.3.
In reply to Ctrl+Z. It requires one to by xavierjazz
Can you make a screencast?
In reply to Ctrl+Z. It requires one to by xavierjazz
I hit Ctrl+Z all the back to score creation / loading, no crash for me.
So it is apparently something unique to your score, so it would be necessary for you to post it - or a reduced version of it if you prefer, as long as it can still reproduce the problem.
In reply to I hit Ctrl+Z all the back to by Marc Sabatella
I now have the score basically how I want it. I'm not too sure what to do to reproduce.
I am changing the was some Bass parts look, using a small staff melody with a large staff Bass part. As I continue with this, I will add more if I discover anything.
Thanks for your swift responses trying to help.
Best,
Don
In reply to I now have the score by xavierjazz
Glad it's working, but definitely update if you figure out a way to reproduce reliably. My personal goal is for 2.0 to release with no known reproducible cases of crashes or corruption. By this metric, I daresay we may actually be *ahead* of 1.3 at this point, although there are plenty of other bugs still left to fix before release.