Thanks for the rapid response. I am working on a new version of my old
spatium issues - I worked with you on those two years ago. I'll be
asking you soon about how you feel about changing the units for these
page sizes and margins from inches to points, as in PostScript points
@72dpi and QPag
Hi,
Sure. As you guessed, the JSON functions are only for a separate storage
mechanism. They are mainly used by the MuseScore.com backend in order to
extract information about the score and display them to the user.
Cheers,
lasconic
Le jeu. 6 déc. 2018 à 17:59, Sideways Skullfinger <
sidew...@si
I just encountered the JSON storage implementation for page settings:
QJsonObject jsonPageformat;
It's part of 3 new functions at the bottom of mscore/file.spp -
saveMetadataJSON() (plus an overloaded version) and exportAllMediaFiles().
Is there a plan to move page settings out of XML and into
FYI - I have found one circumstance outside of pagesettings.cpp in which
the page settings are definitely handled distinctly from the styles: the
class Score constructors. Parts inherit all styles from their master
score, except page settings, which are inherited from the default
MuseScore set
Can someone explain to me how the page settings data fields overlap and
interact with the global styles in MuseScore? I'm looking from an
internal, code-based perspective.
They are in separate dialog boxes for the user. They are stored
together at run time in the styles (Sid::whatever). The
