Repository navigation
Move adding tuplets to the selection into EditTuplet - #35427
Conversation
NotationInteraction::addTupletToSelectedChordRests() gathered the selected chords/rests, divided them into tuplets and set the selection afterwards, out of reach of the engraving tests. Move this unchanged into the new EditTuplet::addTuplets(), which returns the tuplets in score order, and test it. Assisted-by: Claude Code 2.1.310 (Claude Opus 5.5)
|
No actionable comments were generated in the recent review.
|
NotationInteraction::addTupletToSelectedChordRests()gathered the selected chords/rests, divided them into tuplets and set the selection afterwards, all in the notation layer, so none of it could be covered by unit tests.This moves it unchanged into a new
EditTuplet::addTuplets()in the engraving module, like the otherEdit*classes. The notation side now only runs it in a transaction, as, for instance,addBeamToSelectedChordRests()does. The function returns the new tuplets in score order.New engraving tests cover the behaviour from #35267: tuplets in score order, the start of the first tuplet selected with its note value as the input duration, a range kept (also across staves), and one tuplet for a note and its linked copy.
No change in behaviour.
Assisted by Claude Code 2.1.310 (Claude Opus 5.5)