Slurs change when entering a pickup measure
I am running the latest nightly build and am running Windows 8.1. When I changed the first measure of a piece from 4/4 to 3/8, multiple large slurs were added to the balance of the piece and some crescendo markings were moved. Is it necessary to establish the duration of all measures prior to entering markings?
Comments
Can you attach a score that shows this behavior?
Seems to be any score:
1) create score in 4/4 time
2) add two notes to measure 2
3) connect them with a slur
4) change actual duration of measure 1 to 3/4
I wonder if this just started recently or if it's been the case for a while? There were a number of slur-related changes lately (including mine).
And latest nightly build refers to dfabf91, I assume.
ver 2902cf6 downloaded on 1-24-14
Either I broke it last week or it was already broken, but either way, I'm pretty sure it has to do with the area of code I was messing with.
EDIT: I now think the issue is unrelated to the section of code I worked on. But I'll still try to fix this; the code will probably be pretty similar to what I actually was looking at.
...and I'm backing out. I don't see any attempt to fix up spanners at all, so I don't know where it would be appropriate to hook in. This feels a bit too "architectural" for me to feel comfortable. BTW, the issue doesn't just affect measure properties. It also affects regular time signature changes. Not in the part being rewritten - that much *is* handled correctly. That is:
1) new 3/4 score
2) add 4/4 to measure 2
3) add two quarter notes with slur to measure 2
3) change initial time sig to 2/4
Slur in measure 2 moves. Ditto with hairpins.
I also notice that after I've corrected the slurs and hairpins, I can print the file and save it but if I load the saved file the slurs are correct but the hairpins have changed to a jumbled mess.
I think this is a duplicate of #24072: Changing measure actual duration shifts all subsequent spanners
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.