Marc Sabatella

Again, to be clear: that means it *does* work. The command is “get location”, not “reestablish range selection”. In all cases it does that: it gets the location. It’s a...

@Tantacrul - I missed this one last week when I was bumping important accessibilty issues. The issue is twofold: 1) no screen reader feedback on Shift+L (should read the currently-selected...

Definitely not at all critical for sighted users. Pretty important for blind ones, though - without a command like this it's very difficult to keep track of where you are...

FWIW, I saw this yesterday on my Linux laptop with a pretty ordinary display. It only happened with the zoom set to 129%, which is the exact I need to...

OK, just had it happen again, after changing my default zoom to 125%, which made it go away yesterday. Here is what it looks like:  In case it's not...

> Yes, the big minimum size of the MuseScore window is an issue currently. The most problematic thing is the top toolbar, which contains a lot of controls and we...

This isn't a feature request, it's a regression - it has always worked in the past and lots of people rely on it as a way to get all sorts...

I'd definitely be interested in seeing the use cases that people have in mind for wanting invisible instruments to automatically be muted. Personally, for me, I don't think I have...

Makes sense. But either way, the regression where MU3 scores will incorrectly needs to be solved.

Reported again in https://github.com/musescore/MuseScore/issues/10951. I had forgotten about this. Hiding instruments but still hearing them is pretty essential for jazz scores where people use this for rhythm section parts or...