From: Bruno N. <br...@th...> - 2011-04-21 16:36:44
|
On 21 Apr 2011, at 17:32, Pierre Jasmin wrote: > On 4/21/2011 12:24 AM, Pierre Jasmin wrote: >> On 4/20/2011 11:08 PM, Mike Wong wrote: >>> Pierre, >>> >>> Thanks for the info. >>> >>> As there's no specific callback for this so-called 'analysis' pass, Is it up to the developer when to set "kOfxImageEffectPropInAnalysis" flag as 1 and then carry out computation during for example e.g. kOfxActionInstanceChanged callback? >>> >> >> Actually I was working from memory instead of what the header files actually say and I see it says >> that This feature is likely to be deprecated in future releases. So I am not clear. >> >> Right now here we only set param values during interact callback ( like in overlay.cpp example - gPropHost->propSetPointer(effectProps, kOfxImageEffectPluginPropOverlayInteractV1, 0, (void *) overlayMain); in describe action ). You can also maybe maintain instance data. > > I lied we of course also set params in actionInstanceChanged all over the place (particularly for hosts that don't support TypeBoolean and TypeChoice animation) > > I am also seeing kOfxParamPropPluginMayWrite I never noticed before, does not seem any host force us to tag that to each parameter that potentially can paramSetValue. > Shouldn't that also be "likely to be deprecated in future releases" or there is something I am missing here? The theory was that hosts might appreciate that property as a hint, however in practice it seems to be redundant. -- Bruno Nicoletti, Chief Technology Officer The Foundry 6th Floor, The Communications Building, 48, Leicester Square, London, WC2H 7LT, UK Skype: brunonicoletti Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906 Web: www.thefoundry.co.uk Email: br...@th... The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 |