chordnames not propagated to parts if parts generated after score load
Windows 7, GIT commit: 3e51505
I find that "sometimes", upon generating parts from a score containing chordnames, the chordnames are not propagated in the parts. I've been trying to figure out what triggers this, and *may* have found the answer:
1) open attached score
2) file / parts
3) new all
5) view flute part
Result: the chordname is not present, but the staff text is
I can reproduce this every time using this score, which is nothing more than a few notes and chords. However, if I re-create this score from scratch and generate the parts immediately - no loading of score from file involved - the chordnames are propagate correctly.
So it seems that in some way, the way chordnames are represented in the score upon initial entry differs from how they are represented after a load of a score in terms of how they are handled by the part generation. Now, I guess I know as much as if not more than anyone about how chordnames are represented in a score, and I can see how there would be subtle differences here. I'd have to step through in the debugger to remind myself of specifics, but I know what I'd be looking for.
However, I know *nothing* about how the linked part facility works, so I wouldn't know whether I really need to change anything about the chordname representation or if this is just a bug in the linked parts facility.
I kind of suspect the latter, and that it might relate to #18507: some text items modified in score after generation of linked parts not reflected in those parts.