Sorry for spamming multiple lists, but I’m not sure how much overlap there is in readers between Dev and Python.
I’m noticing a strange issue with Nuke’s callback order for nodes created by gizmo files or pasted from other scripts. It seems like any 'knobChanged' callbacks are running before the 'onCreate' callback for these types of nodes. Now, according to the Nuke callback docs, 'onCreate' should be run on all child nodes before it gets run on the gizmo. This seems to be working as advertised, but the piece I’m missing is why 'knobChanged' would be running before 'onCreate' for a given node ever, period. I’ve got a ticket open with support trying to figure out why Nuke is behaving this way, but I figured I’d put something out on the lists to see if someone has crossed this bridge already. Thanks, -Nathan
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
