Casper Jeukendrup

@SolfaMode Sorry to insist, but I'd prefer not merging code that creates technical debt of which it is unclear when and how and by whom it is going to be...

Rebased on their behalf

This issue seems not applicable to MuseScore 4+, which is written completely in QML. Using the software backend by default is no option because of its inferior performance, and the...

We decided to close this issue for now, for the following reasons: - using software rendering for everyone is not really a good idea because of the performance implications, and...

**My proposals** - Introduce a `TextEditingSession` class, that lives in NotationInteraction land. All text interaction logic should be moved to this class. When the user double-clicks a text element, a...

@chrisroode Welcome! It's great that you're interested to contribute. I'll have to discuss with the team whether this is a good issue to get started with or that we prefer...

@XiaoMigros Following on your recent work on the Retrograde plugin, I was thinking it would be nice to get this one in as well. Would you be willing to rebase...

Yes, let's do that!

@XiaoMigros Now that https://github.com/musescore/MuseScore/pull/28505 has been merged, it would be great if you could look into this PR again!

@XiaoMigros While working on https://github.com/musescore/MuseScore/pull/28839 I temporarily forgot about this PR, so now there will be some conflicts in `configure.qml`. Sorry for that!