Nuke always keeps a ‘default’ knob curve around when you start splitting knobs. So if you split off your ‘left’ view, you’re creating curves for ‘left’ and ‘default,’ which, as you can imagine, everything else falls through to. Once you split off ‘right,’ you’re up to 3 curves.
Why they let you split a knob into more components than there are views in your script is a great question... I imagine there was a reason for it when they designed it that way, but I have no idea if that reason is still valid or applicable. -Nathan From: Howard Jones Sent: Wednesday, March 30, 2011 12:56 AM To: Nuke Python discussion Subject: [Nuke-python] more views than actual views Dear All. Does anybody know why it is possible to end up with more curves per view than there are views? That is create a stereo project split off a knob to left right, you get 2 curves, knobs etc knob.le knob split it again and you get knob.le knob.re knob.* the last one is an extra knob beyond the amount of views you have. I can understand from a code pov why when you split knobs in the first place you get knob.le knob and not knob.le knob.re but I cant understand the need for the extra view. Is this a bug or clever behaviour. It means btw if you want to know how many views are in a project you have to add 1 to the result. ie len(nuke.views()) is potentially 1 short unless its safe to ignore the extra one. Howard -------------------------------------------------------------------------------- _______________________________________________ Nuke-python mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________ Nuke-python mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
