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 #281957, fix #297425: Display of beam properties and Dragging multiple selected elements #5494

Merged
merged 2 commits into from
Dec 24, 2019

Conversation

mattmcclinch
Copy link
Contributor

@mattmcclinch mattmcclinch commented Nov 23, 2019

This PR addresses two issues that are mostly unrelated, but they both involve the clickOffElement variable which I have renamed to modifySelection.

First issue: https://musescore.org/en/node/281957#comment-961204
Second issue: https://musescore.org/en/node/297425

Do not deactivate the highlighted beam mode palette cell when the user clicks on the canvas to drag the score. Also, highlight the beam mode for multiple selected ChordRests, if they all have the same beam mode.
Do not deselect other elements upon mouse press if the element under the mouse is selected. This allows for easier dragging of multiple selected elements. The current behavior of deselecting other elements is retained if a drag is not initiated.
@dmitrio95
Copy link
Contributor

This PR reveals a bit unexpected behavior of dragging multiple elements in range selection: if I select a range and try dragging a note in it, not only notes get repitched but also rests, texts and any other selected elements get repositioned. Would it perhaps make more sense to limit dragging to the same element type in range selection (for example, like in this commit) or disabling dragging for range selection at all? This behavior was there before this PR as well, but it was nearly undiscoverable as one had to hold Shift and start dragging to see the same result.

@mattmcclinch
Copy link
Contributor Author

I like the solution in your linked commit, because it allows the user to do what he or she is trying to do, and it does not try to second-guess the user's intent. It would be a shame to preserve the selection but then turn around and disable the drag, which was the alternative that you gave.

@anatoly-os anatoly-os added this to the MuseScore 3.4 milestone Dec 16, 2019
@dmitrio95 dmitrio95 merged commit 08cb101 into musescore:master Dec 24, 2019
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

3 participants