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 #52506: Split Staff on particular slur crashes MuseScore #1933

Closed
wants to merge 1 commit into from

Conversation

lasconic
Copy link
Contributor

@lasconic lasconic commented Apr 9, 2015

In checkSpanner, I make sure that we don't have slurs ending on a rest. The only case where it should happen is during note entry. So when exiting note entry, I delete the pending slur... I know it's a bit weird to do this at this place, so I made a PR. Comments welcome.

@MarcSabatella
Copy link
Contributor

The code makes sense to me, but - I don't think disallowing slurs to rests is a good idea. I suspect a lot of people rely on this to have one-sided slurs that are really "fake" one-sided ties (like into voltas, etc). Or, in older scores (even newer ones), people might be using one-sided slurs to fake falls / scoops etc. Also, the "L.V." / "let ring" indication for stringed instruments?

I guess the crash was because upon moving the note to another staff, the slur was not connected well? Wouldn't it be better to fix the slur rather than delete it? Or, delete it explicitly during the split operation, not as something checkSpanner would do all the time. Not that I know where/how to do that.

@heuchi
Copy link
Contributor

heuchi commented Apr 10, 2015

I get a crash when I press 's' on a note that is followed by a rest, when not in note entry mode.

@lasconic
Copy link
Contributor Author

OK. Thank you both for the feedback. I will try another approach.

@lasconic lasconic closed this Apr 10, 2015
@lasconic lasconic deleted the fix-52506 branch April 10, 2015 09:39
@Jojo-Schmitz
Copy link
Contributor

@wschweer fixed it differently in e384f62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants