Feature request: Disable plugin from Browser or plugin properties

[petemus]

As a chronic GAS person, I have a lot of plugins. I know plugins can be excluded from the Plug-in Manager, but that's a bit hard as you first have to check out what the plugin is on a track or bus and then go to the manager to disable it.

Could it be possible to exclude a plugin within the Browser? That way, grooming the plugin set would be a bit more streamlined. When I come to think of it, an even better place for the disablement command would actually be the plugin menu:

A small feature, but would help (at least me) a lot, I think. Enabling the plugins, when in regret, would happen as it does now, from the Plug-in Manager.

Edited July 8, 2021 by petemus
Improved the subject line

[Mark Morgon-Shaw]

Browser is a better method once you have a lot of plugins.

[petemus]

1 hour ago, Mark Morgon-Shaw said:

Browser is a better method once you have a lot of plugins.

Probably, yes. You could easily drag'n'drop a plug onto a track and decide it's fate and then say goodbye to it easily, if need be.

Edited July 8, 2021 by petemus

[Starship Krupa]

I am in favor of this and any other enhancements to the plug-in Browser.

[Mark Morgon-Shaw]

3 hours ago, Starship Krupa said:

I am in favor of this and any other enhancements to the plug-in Browser.

How about similar to how we have it with the Track Manager...tick boxes for folder and individual plugins. 

Imagine this level of control for what plugins show up