Why does collision detection ignore manual offset?

I recently switched from Musescore to Dorico (Elements) and I love almost everything about it, but this one took me some time to figure out and I simply don’t understand it.

I had a text over high notes on multiple ledger lines and a dynamic marking in the staff above that, which resulted in a large vertical distance. I moved the text to the side to close the gap a little, but initially the spacing didn’t change at all, only when I disabled “Avoid collisions” for the text.

Are there any situations that benefit from collision avoidance not taking into account that an object was moved manually?

I’m not sure why it is the way it is; though I’m Daniel will have explained it somewhere.

But, yes: sometime’s it’s better to just turn off collision avoidance on a text item, if you’re going to move it because things are avoiding it.

2 Likes

The rationale for doing it this way is that it’s guaranteed to be stable. The alternative—where you take the edited position into account—often leads to situations where you make an edit to fix a problem, which causes collision avoidance to re-run, creating a new, different problem, which you now have to fix, which causes collision avoidance to re-run, etc… (We had this problem with Sibelius.)

8 Likes