Peter Sampson

@dozzzzer you can already type the first letter or first few letters of the plugin you want to access in the plugin manager

> Indeed. What a discovery! Thanks for pointing out, @petersampsonaudacity However, it's highly unlikely that an average user would know about it. You're welcome, it's a bit of an Easter-Egg...

> @dozzzzer you can already type the first letter or first few letters of the plugin you want to access in the plugin manager Hopefully one should be able to...

I added Tip divs to the Plugin Manager and the Macro Manager pages in the alpha manual for these selection Easter-Eggs a) https://alphamanual.audacityteam.org/man/Manage_Effects,_Generators_and_Analyzers#Enabling_and_disabling b) https://alphamanual.audacityteam.org/man/Manage_Macros#insert

Ooh - that looks nice Apart from the added Search the GUI is much prettier.

Testing on W10 with @vsverchinsky 's latest branch build for this You have a small typo Vitaly - it should say Di**s**abled  Plus the Consistency>Spelling page in the Manual...

> I don't mind the path continuing to say "Built-in Effect". And indeed the un-hyphenated "builtin" in the Type dropdown is inconsistent with the hyphedated "built-in" in the Path listings...

@LWinterberg Hi Leo, does the "Builtin Commands" in this dialog mean that you have plans to enable/disable menu commands at some stage ?

Tested on @vsverchinsky 's latest test branch for this: audacity-win-3.5.0-alpha-20240220+8603999-x64 All looks good to me now:   _I have added a P1 to the Manual to remind me to...

Note that when you press the **Rescan** button, once the scan had finished all the EGATs in the dialog window are grayed-out  a) Clicking any one of them will...