Plugin API: Add MU4 properties, elements, and enums #28505
+2,055
−506
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #28478
Resolves: #28476
Requires #28502 to build.
Following Changes have been made to the plugin API:
The code style has been updated to more closely match the rest of the engraving module.
All new element types and properties since 4.X have been made accessible to plugins.
Many more enums are now exposed (and declared!), facilitating working with various property types.
A
Cursor
now has a.staff
property (read and write), rather than previously just thestaffIdx
.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 - Yes, with Move some types out of dom to dedicated file #28502
I created a unit test or vtest to verify the changes I made (if applicable)