Editing beams corrupts chord layout
MuseScore 0.9.6.3 and trunk r3599
- Open the attached file.
- Double click on the beam of the second beat
- Move one of the handle
Expected result: The beam angle or position should change without changing the chords
Actual result: The notes in the chords are relayouted.
First report : http://musescore.org/en/node/7630
| Attachment | Size |
|---|---|
| BugLayoutChordBeam.mscz | 1.7 KB |
Comments
I've found the causes!
1) There must be one chord beamed to another chord or a single note. Order doesn't matter.
2) The stems must point downwards.
3) The chord must contain 2 consecutive notes (i.e. a second interval) plus a third note (can be any). Eg: C-D-G, F-A-B, A-B-C...
4) You must move the beam up/down.
Observation 1: that doesn't happen if the chord is not beamed to anything.
Observation 2: this doesn't happen if the stems point upwards, so I guess this situation has a portion of code that already fixes that.
Here I'm putting an example:
Since this does CORRUPT the notation, I think it is worth being classified as critical.
Still happening as of fcdc24be61
Can't reproduce!! Fixed I guess.
![test]( "test")
R.2d3b0b9
Automatically closed -- issue fixed for 2 weeks with no activity.
Not fixed! Stumbled upon the same problem as posted by guifre on January 30, 2012 - 6:37pm. With the same rules. (Reproduced by entering the same chords, same problem in both A-major and C-major. Found the issue in another piece I was working on)
Musescore v1.3 (revision 5702)
Windows 7 64bit
(sorry for reactivating, dont know if it is the right way (first post), but opposed to other issues I ran into this one was hard to find and this was the only issue report I could find on it)
It's actually fixed in the current development version. That's why it's marked as fixed.
Aaahh I see, sorry then, I'll wait until it is implemented in the normal version, thanks for the reply.
Automatically closed -- issue fixed for 2 weeks with no activity.