Casper Jeukendrup

@brobrobrob Welcome! Feel free to work on this issue. You can take inspiration from @mmeyn's pull request (https://github.com/musescore/MuseScore/pull/19157) and the comments there. Additionally this comment may be useful: https://github.com/musescore/MuseScore/pull/15363#pullrequestreview-1322471128. Documentation...

@avvvvve This is definitively ready for testing! We decided to merge the work in multiple steps, and this is the first one. Opening the popup and clicking options in the...

So this PR is the first step, about opening/closing the popup and the basic interaction of clicking options. The second PR will implement the 'drag handle to create hairpin' interaction....

@re1san Some accompanying technical advice: 1. (Keyboard navigation) You have already created a `NavigationPanel`, just like CapoPopup has for example, and it looks like you only need to hook up...

Perhaps that's the best idea, yes. But if a specific item turns out to be difficult to solve, then we can decide together to save that for later, for a...

(the latest push was just a rebase, but nothing besides that)

> Would it be okay if I filed one issue for each of those groups above (rather than individual issues)? Yes, that's fine. Also, maybe the content of those issues...

It looks like some overrides of `subtype()` and `subtypeUserName()` are missing the `override` keyword, causing some compiler warnings. Would be good to fix those

A merge commit has appeared; that probably means that you accidentally pulled instead of force-pushed. A rebase will probably fix it.

I looked at the unsolved issue 4 from above. This is what I just wrote to Michele about this: I’ve figured out the problem. It’s a bit nasty. What happens...