Agree. A list with just an enable/disable option would be far better. Almost no plugin developer takes the trouble of designing an icon for his/her plugins, simply because they are useless.
We need a new category 4.4 (and also 4.5)
This is my Enabled list in MS 4.4.2's Plugin Menu, displaying all the unnamed plugins as Run plugin ( ) :
I'd vote that MuseScore 4 only enabled plugins that have a valid name string. Otherwise identifying the plugin requires trial-and-error guesswork. And one must identify a plugin:
• to enable it
• to run it via MuseScore 4's Plugin menu
• to disable it
The naming is easy to fix, in the plugins.
The issue stems from the different methosds used in MuseScore 3.x, 4.0-4.3 and 4.4+ ans the plugins developers' desire to maintaine onle one version for all 3 of them.
Typical code:
description:"This plugin colors the chords and rests of each voice"menuPath:"Plugins.Notes.Color Voices"// Name for Mu3id: colorvoice
//4.4 title: "Color Voices"//4.4 thumbnailName: "color_notes.png"//4.4 categoryCode: "color-notes"Component.onCompleted:{if(mscoreMajorVersion >=4&& mscoreMinorVersion <=3){
colorvoice.title="Color Voices";
colorvoice.thumbnailName="color_notes.png";
colorvoice.categoryCode="color-notes";}}
description, thumbnailName and categoryCode are optional
A plain Mu3 plugin just needs
description:"This plugin colors the chords and rests of each voice"menuPath:"Plugins.Notes.Color Voices"// Name for Mu3
Sure, but one cannot add a new catagory, hence no new submenu.
In MS3x, menuPath: "Plugins.Notes.Color Voices" adds a new submenu Notes under Plugins.
(and if you name it "NewPlugins.Notes.color Voices" you even have a complete new menu 'NewPlugins"
In MS4.X, you can only choose between the predefined categories. Anything else is ignored and the plugin ends up under Plugins in the menu.
Yes. One could say it's the responsibility of the plugin creator, but I'd hoped that development would create a community project where an "intern" could signup to fix the naming issues in all the "enableable" MS4 plugins.
Comments
+1
From my vantage, MS4's plugin window is a mess:
• Many of the plugin names are blank ... even in the Enabled list.
• I don't understand why the icons so large. Perhaps it's a premature step toward mobile? Or just a pointlessly trendy MuseGroup thing.
• Why isn't there an option for a simple, sortable List View for those of us annoyed by the iconic waste of space?
MS3's method was _much simpler_and clearer ... albeit considerably less grandiose!
On my installation the plugin page takes up 3/4 of my 27" display:
Where as a list or menu would suffice:
Enabled
No title
No title
No title
No title
ABC Import
New Retrograde
Note Names
Tin Whistle
Disabled
No title
No title
No title
Color Notes
Courtesy Accidentals
Lilypond Lyrics
Mirror intervals
Modal Temperaments
Modal Tuning
Tuning
In reply to MS4's plugin window is a… by scorster
Agree. A list with just an enable/disable option would be far better. Almost no plugin developer takes the trouble of designing an icon for his/her plugins, simply because they are useless.
We need a new category 4.4 (and also 4.5)
In reply to Agree. A list with just an… by graffesmusic
4.5 will break 4.4 plugins???
In reply to 4.5 will break 4.4 plugins??? by .ash86
So it seems
In reply to So it seems by graffesmusic
Not yet as far as I can tell
In reply to MS4's plugin window is a… by scorster
I don't think New retrograde wil even run in MU4.x
In reply to I don't think New retrograde… by elsewhere
The New Retrograde plugin works here in MU4.4.2
In reply to MS4's plugin window is a… by scorster
+1 for a sortable List view.
In reply to MS4's plugin window is a… by scorster
This is my Enabled list in MS 4.4.2's Plugin Menu, displaying all the unnamed plugins as Run plugin ( ) :
I'd vote that MuseScore 4 only enabled plugins that have a valid name string. Otherwise identifying the plugin requires trial-and-error guesswork. And one must identify a plugin:
• to enable it
• to run it via MuseScore 4's Plugin menu
• to disable it
In reply to This is my Enabled list in… by scorster
While we are at it: now there are only 4 plugin categories:
static KnownCategories categories {
{ "composing-arranging-tools", TranslatableString("extensions", "Composing/arranging tools") },
{ "color-notes", TranslatableString("extensions", "Color notes") },
{ "playback", TranslatableString("extensions", "Playback") },
{ "lyrics", TranslatableString("extensions", "Lyrics") }
};
Isn't this somewhat restricted? e.g. where to categorize the 'Harmonica tabs' plugin? In composing-arranging tools?
In reply to While we are at it: now… by graffesmusic
Those categories are optional.
But feel free to request more of them on GitHub
In reply to This is my Enabled list in… by scorster
The naming is easy to fix, in the plugins.
The issue stems from the different methosds used in MuseScore 3.x, 4.0-4.3 and 4.4+ ans the plugins developers' desire to maintaine onle one version for all 3 of them.
Typical code:
description, thumbnailName and categoryCode are optional
A plain Mu3 plugin just needs
A plain 4.0.-4.3 plugin only needs
A plain 4.4+ plugin only needs
But one version stumbles accross the methods needed by the others, so you end up with the top example.
In reply to The naming is easy to fix,… by Jojo-Schmitz
Sure, but one cannot add a new catagory, hence no new submenu.
![newplugins.png]( "newplugins.png")
In MS3x, menuPath: "Plugins.Notes.Color Voices" adds a new submenu Notes under Plugins.
(and if you name it "NewPlugins.Notes.color Voices" you even have a complete new menu 'NewPlugins"
In MS4.X, you can only choose between the predefined categories. Anything else is ignored and the plugin ends up under Plugins in the menu.
In reply to Sure, but one cannot add a… by graffesmusic
Yes. As said: feel free to request more
In reply to The naming is easy to fix,… by Jojo-Schmitz
Yes. One could say it's the responsibility of the plugin creator, but I'd hoped that development would create a community project where an "intern" could signup to fix the naming issues in all the "enableable" MS4 plugins.