> But if I try the same with lens_function(), I get no joy. In my case, it
> looks like lens_function() is never even called (as in, I don't get its cout,
> which is still my lame way of debugging) :)
>
> /*virtual*/ LensFunc* lens_function(int mode) const {
> cout << "custom projection func" << endl;
> return myLensFunc;
> }
>
>
> In any case, I was only interested in implementing my own LensNFunc, so it's
> all good. But I'd be interested in knowing whether lens_function() is meant
> to work differently, or if it's just not doing what it should be doing.
That's likely correct, especially since there's only a LensNFunc pointer stored
in the Scene. It's probably a case of lens_func being deprecated in favor of
LensNFunc as it's clearly more efficient to use the array method.
To be honest I can't completely recall the sequence of events re. these
functions...
-jonathan
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
