You do not need to unlock thePict parameter unless you locked it for
some reason.
The return value may need a lock:
If you created the Picture in the function then the reference count
is 1 and no additional lock should be done.
If you are returning thePict (image that you did not create your
self )then you need to Lock it to increase the reference count)
Björn
Phil M wrote:
I have a function in my plugin which accepts a REALpicture, does
something with it and then creates a new REALpicture to return.
Function prototype looks like this:
static REALpicture InvertRGB(REALpicture thePict);
Do I need to free/unlock either the function parameter or the return
value? Or is unlocking only required for a matching Lock request?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
