4

Chapter 30 Installing and Creating Macros 919
Each of these has a default value assigned. Note that the image has 0, which indicates
“no input.”
These values are applied to both the command line or the graphical user interface
defaults. If you do not supply a default argument, you must enter a value when you call
the function. It is therefore recommended that you enter defaults.
The second location is in the ui.h file when the function is called. To override the
startup defaults, enter your own in the ui.h file. Normally, you have something like the
following in your ui.h file:
nuiPushMenu(“Tools”);
nuiPushToolBox(“Filter”);
nuiToolBoxItem(“@SoftGlow”,SoftGlow());
nuiPopToolBox();
nuiPopMenu();
This sets new default values just for the interface:
...
nuiToolBoxItem(“@SoftGlow”,SoftGlow(0,100,.5,1, 95));
...
Attaching Parameter Widgets
If you take a look at “Using Parameters Controls Within Macros” on page 379, and
experiment with different nodes in the interface, you see that you can attach many
behaviors to parameters. This section takes a raw macro and shows different examples
of behaviors to change the parameters sliders to more efficient widgets.
Changing Default Settings
Most of Shake’s functions (third-party development excepted) are stored in two files
in <ShakeDir>/include in nreal.h and nrui.h. nreal.h is the complete list of all functions
and settings. The nrui.h file builds the interface. You can modify these files to suit your
needs, but it is strongly recommended that you make a backup of these files before
you begin. Errors in the file may result in unexpected problems with Shake.
These files are also an excellent source for examples.