Normalised double parameters have proved to be more of a problem than expected. The major idea was to provide resolution independence for spatial parameters. However, in practice, having to specify parameters as a fraction of a yet to be determined resolution is problematic. For example, if you want to set something to be explicitly '20', there is no way of doing that. The main problem stems from normalised params conflating two separate issues, flagging to the host that a parameter was spatial, and being able to specify defaults in a normalised co-ordinate system.
With 1.2 new spatial double parameter types are defined. These have their values manipulated in cannonical coordinates, however, they have an option to specify their default values in a normalise coordinate system. These are....
These new double parameter types are....
kOfxParamDoubleTypeX- a size in the X dimension dimension (1D only), new for 1.2
kOfxParamDoubleTypeXAbsolute- a position in the X dimension (1D only), new for 1.2
kOfxParamDoubleTypeY- a size in the Y dimension dimension (1D only), new for 1.2
kOfxParamDoubleTypeYAbsolute- a position in the X dimension (1D only), new for 1.2
kOfxParamDoubleTypeXY- a size in the X and Y dimension (2D only), new for 1.2
kOfxParamDoubleTypeXYAbsolute- a position in the X and Y dimension (2D only), new for 1.2
These new parameter types can set their defaults in one of two coordinate systems, the property
. Specifies the coordinate system the default value is being specified in.
Plugins can check kOfxPropAPIVersion to see if these new parameter types are supported