+1 650 396 9674

Release details are described below:

Change Log

Fixed a bug in the <Uint8VectorArrayNode> property sheet. Previously, this property sheet enumerated all four vector components, even if the vector dimension was 2 or 3. While this bug could be confusing if the user didn't know that their vec2 was still a vec2 despite displaying all 4 vector components, this bug didn't cause any numerical errors because the <Uint8VectorArrayNode> object's underlying <Uint8VectorArray> object is always a 4D vector in memory.

Fixed inconsistent behavior in the <VariableNode> vector array node derived type property sheets. For example: in <Float32VectorArrayNode>, minimum and maximum vector range properties are always enumerated as a 4D vector even when the vector is 2D or 3D. However, property edits to the 3th or 4th vector component of the minimum and maximum vectors were not completed if the user edited a vector component that was 'out of range'. For example: if you have a 2D vector, you could not change the 3th or 4th vector component even though they were enumerated. The user can now set properties for all the vector components of the minimum and maximum vectors, even if the vector represents a vec2 or vec3.

In type_uint64_node_algorithms.ssl and type_int64_node_algorithms.ssl, fixed a bug that caused value toggle between zero/non-zero to fail because the values were computed but not assigned back to the <Node>.

Adjustments to numeric range algorithms to make sure that the correct range value is calculated when one of the range values is negative. For example: in the <Uint64vectorRange> data interfaces, ::LargerThan( ... ) and ::SmallerThan( ... ) have been improved. Note that the behavior of these and all similar data interfaces is undefined if the range minimum is not less than the range maximum.

Updated sliders for unsigned integer <VariableNode> types. Slider updates remain for signed integer types and floating point types.