Move down element with arrow up?
I don't know if there is a good reason for this, but it feels weird that I have to press the up arrow in the Y axis to move an element down (and that ascending displacement is represented by negative values, for that matter).
Comments
This is what I mean https://imgur.com/a/qeZAECz (I don't know why but I can't attach the .gif directly)
In reply to This is what I mean https:/… by Miguel Vicente…
It isn't a .gif but a .mp4, and those indeed can't get uploaded to musescore.org
In reply to It isn't a .gif but a .mp4,… by Jojo-Schmitz
I guess Imgur changed it into .mp4 but it was originally a .gif. Maybe just too big?
In reply to I guess Imgur changed it… by Miguel Vicente…
There's a size limit too. And yes, 22MB would be way beyond that
In reply to There's a size limit too by Jojo-Schmitz
Test gif
I agree wih you
Having negative Y being up or down depends on the coordinate system used and likely stems from graphic editors, where the top-left corner often is the origin, rather than the bottom-left corner (as is more often the case in euclidean math).
Changing that now internally would become a major breaking feature for all existing scores with (imho) little to no benefit. One may consider changing the user input box values by negating the real values, but that then might simply confuse new code contributors and/or people used to graphical editors.
When you're inside a numerical entry box, pressing up doesn't mean move the element up (as often numeric entry boxes don't relate to position at all), but it simply means increase this value; exactly what is happening now.
If you want your up key to actually move the element up, then put the element in edit mode (double click it) and use the arrow keys on the element itself.
In reply to Having negative Y being up… by jeetee
Thanks for the explanaition.
"If you want your up key to actually move the element up, then put the element in edit mode (double click it) and use the arrow keys on the element itself."
Yes, this would be the optimal solution. It works for some elements (f.i. dynamics) but seems not to work for slurs. If I put the element in edit mode, arrow keys move the hooks not the element. If I only clik the slur once, it is selected but noting moves. Maybe I am doing something wrong?
In reply to Thanks for the explanaition… by Miguel Vicente…
To move the entire slur, use the middle handle, the one in-between the endpoints
In reply to To move the entire slur, use… by jeetee
I see, thank you. I wonder if there is a reason for not being this hook the one selected by default when entering in edit mode? I'd been trying to move the elements with the arrows for some time now and never get to realize this was the solution to my problem.
In reply to I see, thank you. I wonder… by Miguel Vicente…
By default the right endpoint is selected, as that also allows changing the range of the slur using Shift+arrow shortcuts. An operation which is more common when adding slurs after the notes had been entered.
When in Edit Mode, TAB will cycle through the handles for selecting one (in case you don't like reaching for your mouse).
In reply to By default the right… by jeetee
OK, thanks a lot for yoyr help.
MuseScore flips the y axis (for those of us familiar with the Cartesian coordinate system - where y values below the x axis - i.e., the zero y value - become increasingly negative).
Discussed in 2017:
https://musescore.org/en/node/180576#comment-672821
and 2018:
https://musescore.org/en/node/269724
In reply to MuseScore flips the y axis … by Jm6stringer
I see, thank you.