CameraOp derives from AxisOp so every camera is an axis with extra parms. in your case that would have worked for matrix values but not for the camera spefifc values in CameraOp. glad it worked.
On Thu, Nov 20, 2014 at 11:55 AM, Eric Larsen < [email protected]> wrote: > Yup, that did it Thanks! I started with the example code from fisheye > and for some reason that was calling AxisOp::knobs instead of the CameraOp > > On Thu, Nov 20, 2014 at 11:00 AM, Johannes Saam <[email protected]> > wrote: > >> hey, >> can you not call CameraOp::knobs( f ) from your knobs function to get >> them created? and then assuming you know the names of the knobs you can >> access them afterwards to set them? >> >> On Thu, Nov 20, 2014 at 10:36 AM, Eric Larsen < >> [email protected]> wrote: >> >>> g the data and setting the internal members for the projection >>> parameters but I can't figure out is how to display the values back as >>> knobs in the UI similar the standard >> >> >> >> >> _______________________________________________ >> Nuke-dev mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >> >> > > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
