What Can I Customize with Menus?


In Softimage, custom menus can only be built as self-installing plug-ins. Self-installing menus contain a definition (what items will appear on the menu, how it will behave and what it will look like) and any extra custom functions (procedures that run when the matching menu item is clicked) you choose to provide.

Before getting into the details of how to build custom menus, this section provides answers to questions about the structure of menu and their components:

What Can I Put in a Menu?

Everything appearing on a menu is called a menu item. Depending on the menu item's origin (the location from which the command or callback was installed) one of the following symbols may appear beside the label:



the user location

the workgroup location

(no symbol)

the factory location


a custom location (a location specified by the XSI_PLUGINS environment variable)

When you define a menu you can add any of the following items:

Where Can Menus Appear?

There are actually more than 100 different locations you can choose from (see siMenuAnchorPoints for the complete list). These locations are called menu anchor points which you specify during menu registration (see Registering a Custom Menu in Softimage). Anchor points can be used on:

Toolbar Menus

Window Menus

Contextual Menus



Contextual menus occur in both the Scene Explorer and 3d Views


A menu's anchor point is completely fixed once the menu is registered (installed) in Softimage because of the way plug-ins are loaded. During registration, the PluginRegistrar figures out where each menu will go but doesn't actually build anything until the user activates its parent menu.

Are the Contents of My Menu Fixed?

You have the option of creating either static or dynamic menus. Menus are rebuilt every time they are loaded or reloaded in Softimage, but you can also choose to rebuild them every time their parent (the menu on which they are anchored) opens.

For example, you can assign a filter to am item on your menu (using the MenuItem.Filter property) for validating the menu against the target or selected objects before it gets displayed. If the filter criteria is not satisfied then the custom menu item is either greyed out or, if attached to a contextual menu, removed.

Alternatively, you could limit menu items from appearing if certain conditions are not met. For example, your menu Init callback might look like this:

if ( Selection.Count > 0) {
		menu.AddCommandItem( "Add Duck To Water", "AddDuckToWater" );
	} else {
		menu.AddCommandItem( "Drain Tub", "DrainTub" );

	menu.AddCommandItem( "Add More Hot Water", "AddMoreHotWater" );

With this example, if nothing is selected in the current scene when the user opens the menu, only the Drain Tub and Add More Hot Water command entries will appear. If something is selected, the Add Duck to Water and Add More Hot Water command entries appear instead.

By default, menus are dynamic. To make your menu static, you can set the Dynamic parameter to false when you call the RegisterMenu (PluginRegistrar) method inside the XSILoadPlugin registration callback.

Do I Have to Use Self-installing Menu Plug-ins?

Yes. While menus can be scripted or compiled, they cannot be created on the fly (in the Script Editor). You must implement your custom menus as a self-installing plug-in using the correct callbacks. For more information, see Self-Installing Plug-ins.