Nathan and Ivan -- thanks for weighing in guys...
@Ivan, you are correct in that I'm wondering why the script fails to continue
past nuke.scriptOpen() in python but works just fine when opened via
nuke.scriptOpen() in an interactive session...
Perhaps, even more simplified -- why does the following continue:
nuke -t
nuke.scriptOpen('myNukeScipt.nk')
### the script loads successfully and returns an interactive prompt after it
prints errors and warnings -- now do whatever...
print nuke.allNodes()
but the following fails to continue (with some buggy scripts):
nuke -t myNukeScipt.nk
### when attempting this with some scripts you just get kicked back to the
shell prompt after normal error messages and warnings...
Btw, adding a proper "runtime error" exception just gave more verbosity on the
missing knobs (due to missing gizmos)...
I'm thinking this is a bug? If nuke.scriptOpen() works in interactive mode --
the other approaches I mention should, in theory, behave the same... right?
Thanks again,
Jep
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
