The Dopesheet can now show an entire channel group as a single row. To add these "group rows" to the Dopesheet, the groups pane in the channel lister has options for collapsing/expanding the scoped channels of a group in the Dopesheet. Please refer to the pulldown menu of each individual group and the Ctrl-Right mouse menu in the channel groups pane.

The Dopesheet can now show an entire channel group as a single row. To add these "group rows" to the Dopesheet, the groups pane in the channel lister has options for collapsing/expanding the scoped channels of a group in the Dopesheet. Please refer to the pulldown menu of each individual group and the Ctrl-Right mouse menu in the channel groups pane.

The Dopesheet can now show an entire channel group as a single row. To add these "group rows" to the Dopesheet, the groups pane in the channel lister has options for collapsing/expanding the scoped channels of a group in the Dopesheet. Please refer to the pulldown menu of each individual group and the Ctrl-Right mouse menu in the channel groups pane.

The Dopesheet can now show an entire channel group as a single row. To add these "group rows" to the Dopesheet, the groups pane in the channel lister has options for collapsing/expanding the scoped channels of a group in the Dopesheet. Please refer to the pulldown menu of each individual group and the Ctrl-Right mouse menu in the channel groups pane.

A new "Channels..." menu entry has been added to the right-mouse menu of most operator tiles in the network editor. This item brings up a dialog which allows you to scope channels of the operator and/or its descendents/outputs. You also have the option to create a group with these channels.

This dialog can also be accessed by right-clicking on an operator in the channel lister beside the channel editor.

A new "Channels..." menu entry has been added to the right-mouse menu of most operator tiles in the network editor. This item brings up a dialog which allows you to scope channels of the operator and/or its descendents/outputs. You also have the option to create a group with these channels.

This dialog can also be accessed by right-clicking on an operator in the channel lister beside the channel editor.

A new "Channels..." menu entry has been added to the right-mouse menu of most operator tiles in the network editor. This item brings up a dialog which allows you to scope channels of the operator and/or its descendents/outputs. You also have the option to create a group with these channels.

This dialog can also be accessed by right-clicking on an operator in the channel lister beside the channel editor.

A new "Channels..." menu entry has been added to the right-mouse menu of most operator tiles in the network editor. This item brings up a dialog which allows you to scope channels of the operator and/or its descendents/outputs. You also have the option to create a group with these channels.

This dialog can also be accessed by right-clicking on an operator in the channel lister beside the channel editor.

A new "Channels..." menu entry has been added to the right-mouse menu of most operator tiles in the network editor. This item brings up a dialog which allows you to scope channels of the operator and/or its descendents/outputs. You also have the option to create a group with these channels.

This dialog can also be accessed by right-clicking on an operator in the channel lister beside the channel editor.

A new pragma has been added to the VEX preprocessor to allow simple disabling of parameters in the Parameter dialog. The syntax is:

#pragma disable parm [controlparm controlvalue] ...

There may be multiple controlparm/controlvalue pairs on the line. The parameter 'parm' will be disabled if controlparm's current value matches 'controlvalue'. If more than 1 pair is specified, all must match in order for the parm to be disabled.

This pragma may be used multiple times on the same parameter, effectively creating an 'or' condition. ie, #pragma disable color usecolor off #pragma disable color fill off with disable the color parm if either usecolor or fill is off.

Toggle parms either have the value 'on' or 'off'. Menu parms will have the value of the token specified by the #pragma choice statement.

The equivalent dialog script command is: disablewhen { controlparm controlvalue [....] } This command is only valid within a parm {} block.

A new pragma has been added to the VEX preprocessor to allow simple disabling of parameters in the Parameter dialog. The syntax is:

#pragma disable parm [controlparm controlvalue] ...

There may be multiple controlparm/controlvalue pairs on the line. The parameter 'parm' will be disabled if controlparm's current value matches 'controlvalue'. If more than 1 pair is specified, all must match in order for the parm to be disabled.

This pragma may be used multiple times on the same parameter, effectively creating an 'or' condition. ie, #pragma disable color usecolor off #pragma disable color fill off with disable the color parm if either usecolor or fill is off.

Toggle parms either have the value 'on' or 'off'. Menu parms will have the value of the token specified by the #pragma choice statement.

The equivalent dialog script command is: disablewhen { controlparm controlvalue [....] } This command is only valid within a parm {} block.

A new pragma has been added to the VEX preprocessor to allow simple disabling of parameters in the Parameter dialog. The syntax is:

#pragma disable parm [controlparm controlvalue] ...

There may be multiple controlparm/controlvalue pairs on the line. The parameter 'parm' will be disabled if controlparm's current value matches 'controlvalue'. If more than 1 pair is specified, all must match in order for the parm to be disabled.

This pragma may be used multiple times on the same parameter, effectively creating an 'or' condition. ie, #pragma disable color usecolor off #pragma disable color fill off with disable the color parm if either usecolor or fill is off.

Toggle parms either have the value 'on' or 'off'. Menu parms will have the value of the token specified by the #pragma choice statement.

The equivalent dialog script command is: disablewhen { controlparm controlvalue [....] } This command is only valid within a parm {} block.

A new pragma has been added to the VEX preprocessor to allow simple disabling of parameters in the Parameter dialog. The syntax is:

#pragma disable parm [controlparm controlvalue] ...

There may be multiple controlparm/controlvalue pairs on the line. The parameter 'parm' will be disabled if controlparm's current value matches 'controlvalue'. If more than 1 pair is specified, all must match in order for the parm to be disabled.

This pragma may be used multiple times on the same parameter, effectively creating an 'or' condition. ie, #pragma disable color usecolor off #pragma disable color fill off with disable the color parm if either usecolor or fill is off.

Toggle parms either have the value 'on' or 'off'. Menu parms will have the value of the token specified by the #pragma choice statement.

The equivalent dialog script command is: disablewhen { controlparm controlvalue [....] } This command is only valid within a parm {} block.

A new pragma has been added to the VEX preprocessor to allow simple disabling of parameters in the Parameter dialog. The syntax is:

#pragma disable parm [controlparm controlvalue] ...

There may be multiple controlparm/controlvalue pairs on the line. The parameter 'parm' will be disabled if controlparm's current value matches 'controlvalue'. If more than 1 pair is specified, all must match in order for the parm to be disabled.

This pragma may be used multiple times on the same parameter, effectively creating an 'or' condition. ie, #pragma disable color usecolor off #pragma disable color fill off with disable the color parm if either usecolor or fill is off.

Toggle parms either have the value 'on' or 'off'. Menu parms will have the value of the token specified by the #pragma choice statement.

The equivalent dialog script command is: disablewhen { controlparm controlvalue [....] } This command is only valid within a parm {} block.

There have been two new functions added to the expression handling in the CPP processor (which is used by vcc, table parsing, dialog script parsing etc.) strcmp("string1", "string2") access("string1") The strcmp() function has the same semantics as the C function of the same name. The access() function checks for that the filename specified can be read by the current process. This means that it exists on disk and has valid read permissions. For example: #if strcmp("foo", "bar") != 0 echo "foo" is not equal to "bar" #endif

#if access("$HFS/houdini/vex/VEXsop") echo The file "$HFS/houdini/vex/VEXsop" can be read #endif These functions are extensions in the same vein as the environment() function.

There have been two new functions added to the expression handling in the CPP processor (which is used by vcc, table parsing, dialog script parsing etc.) strcmp("string1", "string2") access("string1") The strcmp() function has the same semantics as the C function of the same name. The access() function checks for that the filename specified can be read by the current process. This means that it exists on disk and has valid read permissions. For example: #if strcmp("foo", "bar") != 0 echo "foo" is not equal to "bar" #endif

#if access("$HFS/houdini/vex/VEXsop") echo The file "$HFS/houdini/vex/VEXsop" can be read #endif These functions are extensions in the same vein as the environment() function.

There have been two new functions added to the expression handling in the CPP processor (which is used by vcc, table parsing, dialog script parsing etc.) strcmp("string1", "string2") access("string1") The strcmp() function has the same semantics as the C function of the same name. The access() function checks for that the filename specified can be read by the current process. This means that it exists on disk and has valid read permissions. For example: #if strcmp("foo", "bar") != 0 echo "foo" is not equal to "bar" #endif

#if access("$HFS/houdini/vex/VEXsop") echo The file "$HFS/houdini/vex/VEXsop" can be read #endif These functions are extensions in the same vein as the environment() function.

There have been two new functions added to the expression handling in the CPP processor (which is used by vcc, table parsing, dialog script parsing etc.) strcmp("string1", "string2") access("string1") The strcmp() function has the same semantics as the C function of the same name. The access() function checks for that the filename specified can be read by the current process. This means that it exists on disk and has valid read permissions. For example: #if strcmp("foo", "bar") != 0 echo "foo" is not equal to "bar" #endif

#if access("$HFS/houdini/vex/VEXsop") echo The file "$HFS/houdini/vex/VEXsop" can be read #endif These functions are extensions in the same vein as the environment() function.

There have been two new functions added to the expression handling in the CPP processor (which is used by vcc, table parsing, dialog script parsing etc.) strcmp("string1", "string2") access("string1") The strcmp() function has the same semantics as the C function of the same name. The access() function checks for that the filename specified can be read by the current process. This means that it exists on disk and has valid read permissions. For example: #if strcmp("foo", "bar") != 0 echo "foo" is not equal to "bar" #endif

#if access("$HFS/houdini/vex/VEXsop") echo The file "$HFS/houdini/vex/VEXsop" can be read #endif These functions are extensions in the same vein as the environment() function.

We now have rounded connectors for tiles.

We now have rounded connectors for tiles.

We now have rounded connectors for tiles.

We now have rounded connectors for tiles.

We now have rounded connectors for tiles.

Fixing the saving of handle binding default settings strings.