asattely

Results 32 comments of asattely

> Setting 'join beams' on the second rest here ![image](https://user-images.githubusercontent.com/20604032/209429443-3759ca5c-6297-424a-ba35-e4fedf4ff2e9.png) results in ![image](https://user-images.githubusercontent.com/20604032/209429454-8df93741-6f0f-4ba9-81b3-5629f375ff10.png) where the beamlet should, instead, point in the same direction as the main beam. Sorry this slipped...

> Does this relate to https://musescore.org/en/node/264750 ? It does indeed. As long as the chords have explicit stem direction, the beam will abide by that.

> @asattely Any progress with this? I feel that the functionality is better tested via a vtest, since it just loads the file and makes sure the stem directions laid...

It would be worth a vtest, for sure. At this point we're still playing around with what the actual placement of these small beams should be. As far as `mag()`...

utest was new, is now fixed with rebase

~~This is fixed by PR https://github.com/musescore/MuseScore/pull/15383, please confirm~~ Looks like it's not actually. I'll look into this now

#15383 Now fixes this one, if you'd like to use that build to verify the issue has been fixed

I am working on fixing this one right now, but for now an easy workaround is to highlight the affected measure and press ctrl-R to reset shapes and positions. Let...

That part is there for system objects that have been dropped with the ctrl modifier (voltas, mostly) whose system object flag defaults to `true` but need to be explicitly non-systemobjectified...