"It definitely worked in 3.2. I did lots of plugin work using that version and 3.1."
Note however that with 3.2 already (Windows 10 at least), some cases of difficulties had been reported with the display of the plugins. When reloading the program, a new (empty) line was created with each reload.
Seemed related to the creation of a new workspace, and when checking extra component "Menu Bar", maybe also the other components? Personally, I couldn't reproduce.
QMenuBar::clear() does not delete the corresponding QMenu objects
from the list of its children. Moreover, these QMenu's seem to never
be deleted. This commit deletes the obsolete QMenu objects manually._
Comments
I'm seeing this as well but it was the 3.2.1 release that busted access to plugins. You can only run them from the engine interface.
I can confirm this for 3.2.1. As well as in the latest builds from the master branch.
Wasn't the case for me on 3.2.
Running them from plugin editor as the workaround...
Assigning a shortcut and using that to run them as an easier workaround, apparently they do get loaded but not shown in the menu.
Hopefully this will be patched in real-time? I don't think i'll load 3.2.1 until it is.
See https://github.com/musescore/MuseScore/pull/5185
Well, that's the easy part. Will there be a 3.2.2 very soon?
In reply to I can confirm this for 3.2.1. by Jojo-Schmitz
It definitely worked in 3.2. I did lots of plugin work using that version and 3.1.
-Dale
"It definitely worked in 3.2. I did lots of plugin work using that version and 3.1."
Note however that with 3.2 already (Windows 10 at least), some cases of difficulties had been reported with the display of the plugins. When reloading the program, a new (empty) line was created with each reload.
Seemed related to the creation of a new workspace, and when checking extra component "Menu Bar", maybe also the other components? Personally, I couldn't reproduce.
See the first image of the invoked thread (and the empty lines): https://musescore.org/fr/node/291416
I.e. (and so, now, it's worse)
In reply to "It definitely worked in 3.2… by cadiz1
In my case I'm running on Windows 8.1. I see the issue. I also rebuilt the code on branch 3.2.1 using VS2017 and it had the this issue.
Came up again in #291506: The plugin menu in musescore 3.2.1 doesn't show correctly
Culprit definitly is 5b22d1b for 2.3.1 resp. 968ca5e for master
@cadiz1 reg. the empty plugin menu entries see #286727: Empty entries Menu Bar under Plug-Ins
One more time in: https://musescore.org/en/node/291538
Again https://github.com/musescore/MuseScore/pull/5185
One more: #291557: Plugin menu in french environment
Fixed as per https://musescore.org/en/handbook/developers-handbook/release-notes/rel…
See https://github.com/musescore/MuseScore/pull/5194 for a real fix
Fixed in branch master, commit 6a5a7cbcab
_fix #291460: fix plugins not appearing in menu
QMenuBar::clear() does not delete the corresponding QMenu objects
from the list of its children. Moreover, these QMenu's seem to never
be deleted. This commit deletes the obsolete QMenu objects manually._
Automatically closed -- issue fixed for 2 weeks with no activity.