(Very) Unusual behavior when editing a Part
Windows 10, MS 3.2.3
1) Generated the Onegin part in the attached.
2) Began editing the Onegin part.
3) Using the Inspector (F8), at measure 44 made adjustments to the position of the Common Time time signature.
4) While making the position adjustment, on it's own, the Onegin part re-populated with the entirety of the score, such that it was identical to the main/original part of the score.
5) Undo (CTRL-Z) had no effect on removing the just-added parts (although the position adjustments seemed to be walked back, hard to tell).
6) Clicking on the main score tab (to confirm no issues there!), and then back to the Onegin part, the additional parts were no longer present, it looked the way it should.
7) Repeating steps 2 & 3, step 4 also repeated itself.
8) Clicking on the main score tab, and then back to the part, again the additional parts had disappeared.
9) Repeated steps 2 through 6 one more time, same results as previous.
10) CTRL+S to save and the score crashed, and the Crash Report window appeared.
11) I will copy a link to this thread into the Crash Report comment window.
| Attachment | Size |
|---|---|
| Onegin's Aria.mscz | 71.8 KB |
Comments
I have the same system as you and I'm not seeing the main score in my window when I edit the location of the common time signature in the inspector. How are you changing it. Please give step by step directions for this so I can duplicate your steps exactly. I've tried using the mouse wheel to adjust the x and y offsets, I've also selected the current offset and typed a new one in both the x and y. I've also deleted the current offsets and entered new numbers. Everything has been working as expected.
In reply to I have the same system as… by mike320
Mike320,
First thanks very much for looking into this.
First, I zoomed in quite a bit to get better visibility of the time signature element at measure 44.
Second, after selecting the C time signature by clicking it once, I opened the Inspector and changed the position of the C time signature by clicking the Y position "Up" arrow (reduce vertical offset) to lower the C, as it was positioned a little bit high.
And just to provide closure- it's not happening anymore, I'm not seeing a repeat of the issue.
I have no idea how the software works in this kind of situation, but is it possible a bug was introduced that went away after causing the crash at CTRL+S?
At least, for future reference there is the crash report with the link to this thread.
In reply to Mike320, First thanks very… by marty strasinger
It's possible the bug is not actually related to moving the symbol (the C) but to something else you did, but it did not show itself until you edited the symbol in the part. So something you did before could have made the system unstable and moving the symbol sealed the deal for the crash. Bugs like this are quite difficult to discover. If you run into it again, try to remember what you were doing before. Also, the stack trace that's automatically sent in your bug report might help someone track down the actual cause of the crash.