Tuplets collide with other elements after being moved
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
When dragging most of elements collision detection still works for them unless autoplacement is turned off. However when dragging a tuplet this doesn't work. The following animation demonstrates this, skylines used for collision detection are also shown:
Comments
@dmitrio95 could you please check from scratch? I suspect this behaviour is actual for 2.X scores opened in 3.0 (hairpins are also affected).
No, this is reproducible from scratch.
![Screenshot_20181113_143814.png]( "Screenshot_20181113_143814.png")
One more proof. Fingering text doesn't participate in autoplacement as well.
![Title1234 2018-11-16 11-07-23.png]( "Title1234 2018-11-16 11-07-23.png")
In reply to One more proof: [inline… by Anatoly-os
Fingerings seem to always be ignored in auto placement.
So you should look at all fingerings before you special case them because tuplets crash with them.
Fixed in branch master, commit 75818b6f9f
fix #277647 Tuplets collide with other elemnts after being moved
Automatically closed -- issue fixed for 2 weeks with no activity.