Casper Jeukendrup

You can keep those changes as far as they are still applicable. But be aware of the fact that the root component has been made a StyledFlickable already; so either...

@DmitryArefiev note for testing: the issue linked to this PR was actually already solved in a recent PR for a very related issue, by making the page scrollable. But this...

> Hello there I am testing the latest nightly but I am not able to see any flickering in the appmenu > > I would like to know if this...

There is generally no handling for the different order on Windows. So it will be wrong in all dialogs.

Ah, yes, dialogs in QWidgets that are using QDialogButtonBox will be correct. But other QWidget dialogs and in all QML dialogs, it will be wrong.

@HemantAntony It's indeed worth mentioning, but actually it's just a general problem with more or less all dialog buttons, so one general issue like this is enough.

Reopening, otherwise people start filing duplicates because they can't find it (which already happened in #15570, which contains some additional info by the way)

Related to #15329. Basically, the problem is that we need to determine which fermatas on different staves / voices belong together, so we need to "consolidate" those. Getting this _perfectly_...

> A complication with any sort of system behavior is, the fermatas may well not be on the same beat. This problem is solved by Dorico's model to some extent,...

This fixes all things that can be fixed on our side; for the rest, the "sub-actions" that we use will have to be updated. They will probably fix it in...