Skip to content

Conversation

@lokanchung
Copy link
Contributor

@lokanchung lokanchung commented Jan 3, 2026

Resolves: #27291

Currently when merging rests, regroup rhythm does not consider tuplets. However, current logic won't check if next rest has tuplet or not. Merging non-tuplet rests and tuplet rests eventually removes the tuplet and end up with removing existing notes.

  • I signed the CLA
  • The title of the PR describes the problem it addresses
  • Each commit's message describes its purpose and effects, and references the issue it resolves
  • If changes are extensive, there is a sequence of easily reviewable commits
  • The code in the PR follows the coding rules
  • There are no unnecessary changes
  • The code compiles and runs on my machine, preferably after each commit individually
  • I created a unit test or vtest to verify the changes I made (if applicable)

@zacjansheski
Copy link
Contributor

Tested on MacOS Tahoe 26.2, Windows 11, Ubuntu 22.04.3. Approved
#27291 FIXED

@cbjeukendrup cbjeukendrup merged commit eeb790b into musescore:master Jan 28, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Regroup rhythms" deletes tuplets

4 participants