Crash when dragging object over bar and then frame
1. Open attached score (produced in 1.3).
2. Click on bar 1.
3. 'Add'>'Frames'>'Insert Vertical Frame'.
4. Drag object from palette (e.g. treble clef) to bar 1, continuing to the vertical frame.
Result: Crash.
Note: See attached log.
Using MuseScore 2.0 Nightly Build 53da48a - Mac 10.7.5.
Attachment | Size |
---|---|
Crash when dragging object over bar and then frame.mscz | 2.03 KB |
Crash when dragging object over bar and then frame [Log].txt | 62.69 KB |
Comments
I suspect it will turn out to be related to the fact that in this particular score, the frame bottom margin is very small (1sp) so it practically overlaps the measure, and the acceptDrop code seems confused about where the mouse is.
This issue occurred between August 11, with the correct Nightly (https://github.com/musescore/MuseScore/commit/0c44719a588c505f94c0c7734…) and August 16, with crash (https://github.com/musescore/MuseScore/pull/1137/files)
I can not be more precise because, in this period, there were several days when the Nightlies could not be opened in reason of a font issue. http://musescore.org/en/node/29816
However, looking at (with no guarantee because I have no ability to understand the code unfortunately), the issue could intervene from here:
- https://github.com/musescore/MuseScore/commit/c78951ba3c57cc6ad172913e2…
or (?)
- https://github.com/musescore/MuseScore/commit/3a43976877299ca9508f4e9f4…
or (?)
- https://github.com/musescore/MuseScore/commit/6d46589c5624b4278e5ad80c1…
or (?)
- https://github.com/musescore/MuseScore/commit/88636cbfeef44db5815e30f38…
Hoping not to me completely mistaking, because I almost feel walking blindly! I understand better the notes language that the code language...! But the error "window" is correct I think.
The third one appears most likely - it rewrote portions of the code where the crash occurs. Good work again narrowing it down for us!
Ok, glad to hear. Not knowing how to write code (alas, again...) , it's my only way to facilitate the work of developers. It's a pleasure to help :)
Fixed in a614472df7
Automatically closed -- issue fixed for 2 weeks with no activity.