The clamp VOP now handles vector4 properly.

The clamp VOP now handles vector4 properly.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where hold down space bar in network pane and clicking (without dragging) brings up toolbar and network pane becomes stuck in view state.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

Fixed bug where when loading custom panel files from a hip file that already existed on disk, the custom panel gadget values would be set into the wrong panel.

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

The VEX pow() function now correctly works on vector4 types (as stated in the documentation).

When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments.

Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not.

When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments.

Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not.

When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments.

Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not.

When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments.

Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not.

When writing VEX plug-ins, it's now possible to force the plug-in function to have a return code, even if it modifies multiple arguments.

Due to this change, all VEX plug-ins will have to be re-created, regardless of whether they use the HDK libraries or not.