This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
UI for enabling plugins or assigning them to "extension points" is unclear and needs design #23421
Labels
needs design
Design is needed
P1
Priority: High
plugins
Related to MuseScore's QML plugin framework (NOT VST/audio plugins)
regression nightly
Works correctly in the latest released version and is broken in the nightly builds
UI
Visual issues affecting the UI (not notation)
Issue type
UI bug (incorrect info or interface appearance)
Bug description
In the panel to manage a plugin's shortcut and enabledness, there is now a dropdown to enable a plugin or assign it to an "extension point".
This will need a UI design pass. The main problems with it are the following:
Also, I'm personally still of the opinion that this is not the right way to present these "extension points" to the user. Instead, I'd prefer to see it as a sort of "if this than that" style automation, where you see a list of possible triggers and then assign plugins or other actions to these triggers. Now, it feels like it's the wrong way around, where you have to assign a trigger to a plugin.
Steps to reproduce
Screenshots/Screen recordings
MuseScore Version
master (4.4)
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
*
Additional context
No response
The text was updated successfully, but these errors were encountered: