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 #40846: require Ctrl+drag to create staff-only barline change #1510

Merged
merged 1 commit into from
Dec 10, 2014

Conversation

MarcSabatella
Copy link
Contributor

In 1.3, you could change to a double bar or other barline style by clicking the barline then double clicking the palette icon. In 2.0, this behavior has changed - the abrline is applied only to the current staff. Unless you know the trick of dragging the palette icon to the measure, it looks like you need to apply the barline to each staff one at a time, which would be as bad as when we had to apply key signatures one staff at a time in 1.3. Worse, barlines applied in this manner "hide" repeat barlines, leading to the issue at hand: http://musescore.org/en/node/40846

Since we have already established the convention with key & time signatures of having ordinary drop affect the whole system but Ctrl+drop affects just the current staff, I have implemented this for barlines as well. I am keeping the special casing for the "tick" styles - they always affect the current staff only even if dragged to the measure.

I tested this as well as I could, but I admit I don't understand all the ins and outs of the barline implementation. But I can verfy that drag of each barline from palette to a measure works as expected, as do Ctrl+drag and double click.

@lasconic
Copy link
Contributor

lasconic commented Dec 7, 2014

Maybe @mgavioli has some insights?

lasconic added a commit that referenced this pull request Dec 10, 2014
fix #40846: require Ctrl+drag to create staff-only barline change
@lasconic lasconic merged commit 3fca041 into musescore:master Dec 10, 2014
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.

None yet

2 participants