Dragging text to new position often makes it jump to different system
In recent updates (currently on 4.5.1.250800846 under MacOS) I have been encountering a frequent issue on many scores. When I try to reposition a text object (such as a rehearsal mark) by dragging it, the object will often suddenly jump to a different system, often far up or down the page. Attempting to drag it back causes a hopscotch from system to system. I am often unable to get it back to where it started and use 'undo' instead. I can reduce this symptom (but not eliminate it) by turning off 'auto-place' on the object. This is frequent, and a significant inconvenience. I don't see any mention of this issue in recent reports, but perhaps I'm just not spotting them. Is this already a known issue? Or perhaps this is an artifact of an older score, or a sign something is misconfigured on my installation. Thanks for any insights.
Comments
"Is this already a known issue?"
Oh yes, reported multiple times, see: https://github.com/musescore/MuseScore/issues/27101
It's already fixed for the upcoming version 4.5.2 (to be released in a few days). You can even test it here: https://musescore.org/en/node/377615
If you prefer to wait, the workaround is : instead of moving these texts with the mouse, use the arrow keys.
In reply to "Is this already a known… by cadiz1
Thanks much. I don't know why I didn't spot it. I think I'm still looking for reports the way we did it in the dark ages. Oh, I see, I guess I should be going directly to GitHub rather than looking through the forum here. Thanks again.
In reply to Thanks much. I don't know… by spinality
No, if you don't find a given issue on Github, it's still best to report it here first. The issue may not be a "bug"; you might simply be making a mistake. The issue might be a bug but it has an existing report that you missed (as you did shrug). Almost always best to report here first.
In reply to No, if you don't find a… by TheHutch
Thanks, yes, but I presumably should still look on GitHub first, to see if it’s been reported…which I forgot to do. (Or perhaps you’re saying it’s described here too, but I missed it…shrug…nothing surprises me anymore.)