Skip to content

fix: use current measure number as initial value in set measure number dialog - #480

Draft
FelipeDefensor wants to merge 2 commits into
devfrom
fix/471-measure-number-initial-value
Draft

fix: use current measure number as initial value in set measure number dialog#480
FelipeDefensor wants to merge 2 commits into
devfrom
fix/471-measure-number-initial-value

Conversation

@FelipeDefensor

Copy link
Copy Markdown
Collaborator

Summary

  • Prefills the "Set measure number" dialog with the measure number of the first selected beat, instead of always defaulting to 0.

Test plan

  • Right-click a beat, select "Set measure number" — dialog should open pre-filled with the current measure number for that beat.

Closes #471

@FelipeDefensor
FelipeDefensor force-pushed the fix/471-measure-number-initial-value branch from 40b1efc to d8b5045 Compare May 6, 2026 15:54
@FelipeDefensor

Copy link
Copy Markdown
Collaborator Author

Add tests for this.

Serve discards the arguments a request is made with, so the dialog itself
has to be mocked to assert what it is prefilled with. Without that, the
initial value could be dropped entirely or read from the wrong measure
and the whole suite would stay green.

Also pins the multi-measure behaviour, which is easy to misread now that
the dialog opens on an existing number: the initial value comes from the
earliest selected measure, and accepting it sets every selected measure
to that number.
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.

1 participant