Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #141581: Jianpu linked staff display and saving to XML score file #3614

Closed
wants to merge 1 commit into from

Conversation

ericfont
Copy link
Contributor

@ericfont ericfont commented Apr 6, 2018

This is a rebase byan61's Jianpu PR #2957 from May last year. I had to resolve a few conflicts and made a few small changes just to make it compile and run. I'm simply posting it here so others can look at the design and think about ways it might be redesigned or improved upon.

nnote = fac->cloneNote(onote, link);
else
nnote = new Note(*onote, link);
add(nnote);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is also unusual because that JianpuChord class inherits from regular Chord anyway, so that already accounts for one copy of each note of the chord. But then this code adds the notes again, which seems redundant.

@lasconic lasconic mentioned this pull request Apr 6, 2018
@ericfont
Copy link
Contributor Author

ericfont commented Apr 7, 2018

I'm not surprised this broke a lot of tests. There were quite a few changes made in the past year.

@dmitrio95 dmitrio95 added the archived PRs that have gone stale but could potentially be revived in the future label Mar 11, 2020
@dmitrio95
Copy link
Contributor

Needs actualization for current master.

@dmitrio95 dmitrio95 closed this Mar 11, 2020
@kennethlimcp
Copy link

Hey @dmitrio95 what was the conclusion for this PR? Will it be implemented?

@dmitrio95
Copy link
Contributor

This PR had a lot of conflicts with the current state of MuseScore code and needs a relatively large amount of work to make it possible to merge it. That's why I archived it, I didn't mean to make any conclusion regarding its implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archived PRs that have gone stale but could potentially be revived in the future
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants