Standard version: 2.0
This is complement to: kOfxParamPropModifiable proposal
The purpose is to list possible ambiguities in API regarding parameters
1) Apparently we do not specify that we expect Boolean and Choice to be "step" animation (as opposed to linearly interpolated as if they were regular int) so where option = 1 @ t=1 and option = 3 @ t = 100 , so @t=99, option should still be equal to 1
I am not quite clear what string animation is interpreted (seems it would be swap at KF too) - currently these parameter types are affected.
2) Removed discussion about kOfxParamDoubleTypeAngle
The doc (not the header file) says it's in degrees so it's always 360 degrees basis for an host that would implement a UI rotation widget - the wors that can happen is the widget points the wrong way (-180 to 180 vs 0 to 360...).
3) I am not quite sure what this means in context of UI versus render thread...
|/** @brief A private data pointer that the plug-in can store its own data behind.|
|- Type - pointer X 1|
|- Property Set - plugin parameter instance (read/write),|
|- Default - NULL|
|This data pointer is unique to each parameter instance, so two instances of the same parameter do not share the same data pointer. Use it to hang any needed private data structures.|
#define kOfxParamPropDataPtr "OfxParamPropDataPtr"
No comments on this change yet