MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
While investigating #24723 three problems were identified and addressed in this PR:
A temporary "filename" with .mscx extension that should be .mscz (but immaterial)
BackendApi::parseTransposeOptions was not setting options.interval and options.key before returning
Since 4.0,Score::transpose only applies to a selected range. In the GUI, this is accommodated by selecting all when the TransposeDialog is opened without a selection. Because the CLI will never have a selection, treat it like opening the TransposeDialog with no selection and replicate the behavior of selecting all.
Resolves: #24723
While investigating #24723 three problems were identified and addressed in this PR:
A temporary "filename" with
.mscx
extension that should be.mscz
(but immaterial)BackendApi::parseTransposeOptions
was not settingoptions.interval
andoptions.key
before returningSinceScore::transpose only applies to a selected range. In the GUI, this is accommodated by selecting all when the4.0
,TransposeDialog
is opened without a selection. Because the CLI will never have a selection, treat it like opening theTransposeDialog
with no selection and replicate the behavior of selecting all.[x] I signed the CLA
[x] The title of the PR describes the problem it addresses
[x] Each commit's message describes its purpose and effects, and references the issue it resolves
[x] If changes are extensive, there is a sequence of easily reviewable commits
[x] The code in the PR follows the coding rules
[x] There are no unnecessary changes
[x] 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)