MuseScore 0.9.6.3 & trunk
- Create a score without title or subtitle
- You should see only one system
- Put quarters in the whole score
- You have two systems
- Drag and select the whole music
- Press Delete --> Crash on trunk
- Undo --> Crash on MuseScore 0.9.6.3
Comments
fixed in r 3658
Backported in branch...
Automatically closed -- issue fixed for 2 weeks with no activity.
Crashes after step 7 on both 1.0.0 pre-release 2 (3949) and 2.0.0 nightly build (3953).
Using Mac 10.4.11.
Don't crash MuseScore 1.0 on Windows.
Still crashes on 1.0 and 2.0 nightly build (4079) - using Mac 10.4.11.
Also see original report .
It crashes on 1.0 and 2.0 nightly build (4079) - Mac 10.6.6.
Crash confirmed using r. 4088 nightly build, Windows 7
Crash after step 6.
Using 2.0 nightly build (4095) and Mac 10.4.11.
Just wondered why it was reinstated in the release notes?
fixed in r4152
Still happening, I'm afraid :)
Doesn't crash for me (Tested using r. 4156 nightly build, Windows 7)
I know why.
(Using David's steps better tailored to the problem: #7729: Delete, undo crash for pages with multi-text frames - close this and re-open David's perhaps?)
1. Create a new score with at least a Title and Subtitle.
2. Shift-drag to select all the elements on the page including measures and text frame.
3. Edit > Delete Selected Measures.
Using MuseScore 2.0 nightly build (4156) - Mac 10.6.7.
(If there's no crash, continue onto 4)
4. Edit > Undo.
Confirmed using chen Lung's steps in comment #14 (above).
Thanks.
Apologies for not providing the exact steps beforehand.
#14 describes a different bug. Fixed in r4160.
Fixed generally. However, it's still happening if you have a score with hide empty staves enabled (maybe a different bug report?).
1. Open score .
2. Hide Empty Staves.
2. Drag-select all the notes on the page.
3. Delete.
4. Undo. (you may not reach this step)
Using MuseScore 2.0 nightly build (4172) - Mac 10.4.11.
#18 is a slightly different bug - it appears to be fixed, however.
Using MuseScore 2.0 nightly build (4233) - Mac 10.4.11.
Automatically closed -- issue fixed for 2 weeks with no activity.