-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix import of default chordnames style in MuseScore 1.3 files
- Loading branch information
Showing
2 changed files
with
7 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1064,6 +1064,10 @@ void StyleData::load(XmlReader& e) | |
else | ||
_customChordList = false; | ||
_chordList.clear(); | ||
} | ||
|
||
// make sure we have a chordlist | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
MarcSabatella
Contributor
|
||
if(_chordList.isEmpty() && !chordListTag) { | ||
if (value(ST_chordsXmlFile).toBool()) | ||
_chordList.read("chords.xml"); | ||
_chordList.read(newChordDescriptionFile); | ||
|
I take it this is part of the fix for the default chordList issue. I'd like to understand better what the overall strategy is. Seems this code will mean we always load a chord list immediately upon loading the score or a new style file. Does this mean the old strategy loading it on demand on the first call to score()->style()->chordList() is no more? I can't say I'll miss it, but I wanted to be sure I understand what's supposed to happen.