asattely
asattely
Resolves: https://github.com/musescore/MuseScore/issues/12785 Beams starting or ending on rests are now rendered properly. This extends to cross-staff beams as well!
 This beam's start position is in a 'floater' position, but was still considered outside the staff, so it was fine for pointers. Now, that is an invalid beam position...
The issue:  I've taken this opportunity to factor out some of the beam-specific code into more generic beam/trem methods. Eventually the plan is to refactor the whole thing to...
Due to a few missed cases, the 1/4sp slant has not been treated as a constraint, in certain situations involving a lot of other beam adjustment to avoid wedges and...
The issue: https://user-images.githubusercontent.com/89263931/191334637-d7be94a8-1886-4186-891e-0b98dcf3264b.mp4 Notice how the slur adjusts for a tie that starts on the same note, but is not at the vertical position to be adjusted for. This has...
The issue:  With snapping turned on, beams would snap to weird different places. This was due to the fact that it was applying snapping to the anchor's page position,...
The new "Gradual Tempo Change" system objects were setting all instances of themselves to staff zero on layout. This is unnecessary, as they and their clones are added to the...
Beams were being unnecessarily lengthened, when the outside beam that slants away from the staff is in floater position  That's been fixed, and now the primary beam can be...
The issue:  Traditional tremolos had no mitigation for becoming extremely small (and in some cases negatively long). This PR caps it at 0.6sp until the gaps become less than...
Traditional flags on notes are reduced outside the staff such as to make sure the hook ends up at a certain vertical point, but this is meaningless for straight flags....