Another option in case,
If all you need to do is more like image processing rather than diving
deep down in the nuts and bolts of Nuke, you can consider instead the
OFX development pathway which is well supported by Nuke. Because OFX has
a C interface it's not subject to issues of compiler version... and it
works just fine to debug with OFX plugins.
Pierre
On 4/24/2013 3:37 AM, Thomas Obermaier wrote:
I also encountered different behavior and availability in validate()
and such, had 2 code paths in the first place but stopped using the
debug mode after some time, it was way too wacky to use. (speaking of
Nuke 6, mainly)
Am 13.04.2013 03:13, schrieb elveatles:
I've been trying to get started with writing Nuke plugins by reading
through the developer guide. Everything is working just fine except
debugging. I go to Tools > Attach to Process, click on Nuke 7.0exe,
then I adjust a slider on the Iop plugin I created. It hits the
breakpoint I set, but all the values I'm seeing in locals are
completely bogus. In draw engine, the 'r' variable is something like
716213616, and all the instance variables are 0 or false, whether I
set them to that or not.
I'm using Microsoft Visual C++ 2010 Express with Windows SDK 7.0
installed so that I can build for 64-bit Nuke 7.0. I'm on Windows 7.0
and building for Release like the documentation suggests.
Any ideas are greatly appreciated since working out bugs feels like
shooting in the dark at this point.
_______________________________________________
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
