When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly.

When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly.

When doing a "Create Type From" operation on a subnet operator, the default parameter values for float type parameters would sometimes appear as "" instead of "0". This would result in bad initial parameter values. Now the defaults are properly set to "0", and the case of float parameter defaults of "" is handled properly.

Fixed a core dump causing bug in the tree Curve control.

Fixed a core dump causing bug in the tree Curve control.

Fixed a core dump causing bug in the tree Curve control.

Fixed a core dump causing bug in the tree Curve control.

Fixed a core dump causing bug in the tree Curve control.

Fixed a core dump causing bug in the tree Curve control.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Previously when specifying "#pragma choice" for an integer parameter, the first token had to be "0", the second "1", and so on. This limitation has now been removed. However, the token strings are ignored, and only the order of the strings matters when determining the value of the integer parameter.

Fixed the rate matching options in the sequence COP.

Fixed the rate matching options in the sequence COP.

Fixed the rate matching options in the sequence COP.

Fixed the rate matching options in the sequence COP.

Fixed the rate matching options in the sequence COP.

Fixed the rate matching options in the sequence COP.

A case where the AttribTransfer SOP combined with a Merge could result in putting uninitialized data being put in the pCaptData attribute has been fixed.

A case where the AttribTransfer SOP combined with a Merge could result in putting uninitialized data being put in the pCaptData attribute has been fixed.

A case where the AttribTransfer SOP combined with a Merge could result in putting uninitialized data being put in the pCaptData attribute has been fixed.

A case where the AttribTransfer SOP combined with a Merge could result in putting uninitialized data being put in the pCaptData attribute has been fixed.