Augmentation Dot offset
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
I'm not able to change the position of the dot. All other will work. But not even when I disable the automatic position if the dot it's not working!? And it also seems to be the case that you cannot do anything else than change if you want the dot above or below thats the only thing what I can see work here in this case. I will the photos below, the first one is the correct one.
| Attachment | Size |
|---|---|
| IMG_20230216_005755.jpg | 94.44 KB |
| IMG_20230216_005541_HDR.jpg | 3.13 MB |
Fix version
4.0.2
Comments
See https://github.com/musescore/MuseScore/issues/16210
In reply to See https://github.com… by Jojo-Schmitz
I signed up for that site but I didn't got much smarter than here?
Score needed, but at least in Mu3 you can change the offsets of the dots to your liking
In reply to Score needed, but at least… by Jojo-Schmitz
I know that in musescore 3 it work very well. Don't understand why it doesn't work in the new one but...:S Shall I send you the score?
In reply to Score needed, but at least… by Jojo-Schmitz
Here is the score at last
Interesting, when you try to change the dot's offset vie the Propertied tab, instead it moves the notehead
Seems a known issue, see https://github.com/musescore/MuseScore/issues/11059
In reply to Interesting, when you try to… by Jojo-Schmitz
Yes. Basically you can change everything else than the Dot. Yes it thinks it's the head of the note....
But right-click > Edit, then using left arrow, moves it
In addition you'd need to move the note/chord left a bit too
Actually https://github.com/musescore/MuseScore/issues/16124, and (will be) fixed in 4.0.2
In reply to But right-click > Edit, then… by Jojo-Schmitz
that's neither correct..
But can be made correct
In reply to But can be made correct by Jojo-Schmitz
Gr8 man! Thanks. Hope this will be easier in next version..
See https://github.com/musescore/MuseScore/issues/16394 for getting this fixed automatically
Automatically closed -- issue fixed for 2 weeks with no activity.