Casper Jeukendrup

@igorkorsukov @shoogle @mike-spa I thought I'd quickly mention you, so that you know about the existence of this list, since you doubtlessly have ideas about this too.

Assigning this to the 4.1 project, since 4.1 will be the first chance to make changes to the file format.

What bothers me about "3.7" is that it seems a (protest) action _against_ the development of MuseScore, instead of something to _support_ MuseScore. Instead of advertising 3.7, you could also...

(Before everyone gets very angry, let me make clear that I understand that all your ultimate intentions are surely good; but it's just about how the "3.7" project comes across...

@MarcSabatella If you have a potential solution, feel free to make a PR for it. I don't have much time for coding the next few days. Also, as a small...

Well, you are correct, but Uncrustify is (pretty wildly) wrong! See https://github.com/musescore/MuseScore/actions/runs/3849233551/jobs/6557988913#step:3:2779 for what it wants you to do. Unfortunately, Uncrustify is the boss...

The code style check uses version 0.73 of Uncrustify, so you might want to make sure that your commit hook uses that too. (We decided that it's the most convenient...

I think part of this PR is still needed to deal with existing scores from 4.0.0 where it is wrong (i.e. scores that already contain ```xml ```

Another idea about the Soloist button: I'm wondering why it isn't a checkbox... doubtlessly there is a reason for that, but I can't remember it.

Nice idea! For the non-checked hover state, I would probably use a simple empty box rather than the "x" mark. The only difficulty is that we need to do something...