Thats bad in quiet a few ways. The most obvious being the result of editing a nodes label, it causes its hash to get invalidated.
You will be messing up the artists undo stack as well as flagging the script as *modified*. I can guarente that artist will not be zooming around there script looking at Write nodes to see how far along a Rush render is. Put it in a panel. On Mon, Feb 28, 2011 at 6:43 PM, Farhad Mohasseb < [email protected]> wrote: > Hey guys, > > I've wrote a small script that returns rush render data to the write node > based on the job it was submitted from. > > Is there a way to have this script running in the background on > time.sleep(60) to ping rush and update the write node label in a while loop > or any other loop once every 60 seconds? (While loop would be while done% < > 100%) > > The problem I have right now is that the code works fine but it locks up > nuke, not allowing anything to be processed by the user until the script is > 100% done. > > O one more thing is there a secret way of updating lists in nodes while the > inpanel is False? > Eg. readGeo2 can have the file set to fbx but the fbx_node_name doesn't > update until the panel is opened. > > Any help would be greatly appreciated. Thanks! > > Cheers, > Farhad > > _______________________________________________ > 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
