Why not just store the Group nodes in a DB table with non-recycled show
indices and load everything from there?
-Nathan
-----Original Message-----
From: Blamsammich
Sent: Thursday, March 24, 2011 9:11 AM
To: Nuke Python discussion
Subject: [Nuke-python] pulldown lists, db's and group nodes
I am having an issue that I am not sure where to begin in fixing. I hope
you all might be able to shed some light on the problem.
I have created a group node that uses some onCreate code to populate a
pulldown knob with the list of active show names. I am using group node in
the pipeline, so this nodes defines a color grade for a shot or show. I
then publish this node out to production using the nuke.nodeCopy() command.
The issue I am having is that if we remove a show from the db due to
completion etc, and I pull back in this group node via the pipeline scripts
when it was saved out with a different count in the index of that pulldown
knob. It causes the node to not load properly or at all since the db index
for that pulldown knob is different than what it was saved with.
now when working with that pulldown knob on the python internals of the
group node, I am never working with the index value of the pulldown but
rather just populating it with a list of show names. but nuke seems to have
an issue with this and the index being different. It seems to be something
behind the scenes that I am not controlling effectively or at all.
if anyone has any suggestions it would be greatly appreciated.
Thanks!
Justin
_______________________________________________
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
