Quickly execute handlers which are found in the currently open stage movie from this menu.
Holding the Option/Alt key pressed, while selecting a menu item opens the script and highlights the handler in the editor instead of executing the handler.
Holding the Shift key pressed copies the syntax into the clipboard instead of executing the handler. So you can paste it in the script you are currently working in.
You can constrain the handlers which get listed in the "Handlers" menu using the search field. Now only handlers containing the string in the search field will be listed in the menu. If the search string starts with the reserved character "*" the search is executed as "match starts with chunk", if the search-string ends with "$" the search is executed as "match ends with chunk".
There is also a "Utilities" menu with some of my authoring helper handlers, which I frequently use, but don't have in the castlib of every movie, as I do not use them at runtime. So instead of adding the script to my movie, to have the handlers appear in the "Handlers" menu, I simply have some "built-in" functions.
Access and control both menus via the keyboard. Ctrl+TAB opens the "Utilities" menu and Ctrl+Shift+TAB opens the "Handlers" menu. It may take some milliseconds to register the key-events, as I don't get keyDown events in an inactive MIAW, so I poll them on a regular basis. This also means, that the menu appears even, if director is in the background :-( If you want to disable the keyboard-control just uncomment it in the framescript "keyboardNavigation_FrameLoop" (member(2,1)). Once the menu is showing you can use the cursor keys to navigate the menu and the RETURN key to execute.

Important Note!
This movie calls the sleep method of the UIHelper xtra on idle, as otherwise the CPU usage would permantly be very high and not only consume my powerbook battery power, but also heat the computer up and make the fan spin as if there is no tomorrow. In order to avoid that stupid behavior I spin the performance down making the engine release the cpu for 1 tick on mac (1/60 second) and 1 millisecond on a windows PC on every idle event. This impacts the playback speed of your movie too. So keep in mind, to close the tool miaw, if you make performance tests with your movie. Or, if you prefer, turn this feature of by simply commenting the line in the "on idle" handler in the first movie script.

Requirements:
This movie requires the Xtra "BuddyMenu" from Gary Smith, the maker of many great Xtras, like for example the indispensable "BuddyAPI". Get it the latest version at: http://www.mods.com.au/BudMenu/index.htm

In order to open the script editor and highlight the match (selecting a handlername in the menu while pressing the Option/Alt key) the UIHelper xtra (Win: JavaUiHelper.x32) is required.
The UIHelper Xtra is one of the standard Xtras, which were delivered with Director until version 8, as part of the 'save as java' xtra components.
The UIHelper xtra is also in the standard-install of Director MX and MX2004. Director 8.5 is missing the xtra, but fortunately the UIHelper Xtra from version 8 works with 8.5 as well. If you use "HandlerMenu" with D 8.5, copy the UIHelper Xtra from previous versions over to your D 8.5 Xtras folder.
Note: You need to have the java components installed in Director 8 for the UIHelper Xtra (Win: JavaUiHelper.x32) to appear in your xtras folder. You'll find the installer on your D8 CD
(Mac: run 'Install Java Components' from the rootlevel of the D8 CD;
Windows: run setup.exe which is contained in the folder 'Java Components' on the root level of the D8 CD).

Some of the built-in "Utility" handlers also require Xtras. These are mostly the standard Xtras, but some handlers require Valentin Schmidts great Shell Xtra. Get it at: http://staff.dasdeck.de/valentin/xtras/shell/

Since this movie is an opensource project you can put your own Utility handlers into it, which may require other xtras.
If you want to add your own built-in handlers, add them to the parentscript "alexUtilities" and add the handlernames to the behaviorscript "simpleBMMenu", just like the already existing handlers. Two things to keep in mind:
1.) the parameters are parsed form the menu string, so add the required parameters to the string, which appears in the menu, just like the other menu items.
2.) the parentscript is executed from within the scope of the stage movie. So every member and other script you refer to in your Utility handler istaken form the castlibs of the stage movie rather than form the castlibs of this movie.

If you like this movie you may also want to take a look at my modification of the Start Page.dxr movie, in order to auto-open the last opened document and also auto-open your favorite Athoring Tool Miaws, like for example "Handlernames" or "3DPI" or "Scenelist" or "FindAll" :-)

I hope you enjoy this movie
Alex da Franca
http://www.farbflash.de