You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mismatch is annoying for developers but doesn't cause problems for end users. If we want to fix it, the Sid should be renamed to match the XML tag rather than the other way around, because changing the XML would cause compatibility problems. (However, for the duplicates mentioned above, we have no choice but to change the XML tag.)
Possibly the XML tags should be generated by a pre-processor macro to ensure they match the Sid names.
In cases where the mismatch is intentional, the macro could take an extra argument, or those cases could be written out explicitly like they are now.
The text was updated successfully, but these errors were encountered:
Issue type
Engraving bug (incorrect score rendering)
Bug description
These XML tag names are duplicated in
src/engraving/style/styledef.cpp
:"measureNumberPosBelow"
Sid::measureNumberPosBelow
Sid::mmRestRangePosBelow
"minVerticalDistance"
Sid::minVerticalDistance
Sid::skylineMinHorizontalClearance
"systemOffsetType"
Sid::systemTextOffsetType
Sid::staffTextOffsetType
As a result, MuseScore cannot tell the difference between these style settings when reading and writing score files.
This problem would manifest as an engraving bug for end users.
Steps to reproduce
Run this command in MuseScore's source folder to see duplicated XML tags:
Screenshots/Screen recordings
No response
MuseScore Version
master
Regression
No.
Operating system
All
Additional context
This command shows XML tags that don't match the Sid name:
Command output (click to show/hide)
Sid name on the left, XML tag on the right
The mismatch is annoying for developers but doesn't cause problems for end users. If we want to fix it, the Sid should be renamed to match the XML tag rather than the other way around, because changing the XML would cause compatibility problems. (However, for the duplicates mentioned above, we have no choice but to change the XML tag.)
Possibly the XML tags should be generated by a pre-processor macro to ensure they match the Sid names.
In cases where the mismatch is intentional, the macro could take an extra argument, or those cases could be written out explicitly like they are now.
The text was updated successfully, but these errors were encountered: