Re: [Nuke-python] Properly creating Obsolete Knobs

[John RA Benson]

You are definitely not crazy - at least concerning your question. The fun part is creating a knob that you didn't know is Obsolete (Array?) and the KnobType somehow changes from what the docs say should be 9 to the Obsolete value of 0. I just noticed in 6.3v5 that at least when pasted, the knob didn't drop out, but it became +INVISIBLE when pasted. So maybe since whatever knob you created ended up being a 0, it wouldn't accept a matrix or string or whatever values a type 0 accepts? Turning off the +INVISIBLE, the array knob i created shows up as an [Unlinked LinkKnob]... jrab Nathan Rusch wrote: Am I crazy, or is it impossible to create an Obsolete Knob properly without using C++?   The GUI method just eats whatever script you set to run when the knob is set, and the Python wrapper exposes no functionality for setting up an execution script. Thus, when the knob is loaded/pasted, it generates an error, a la:   "Obsolete_knob foo call is wrong, probably missing NULL for script argument."   -Nathan _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python

_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python