Hmmn -
aha - after a bit of testing... it doesn't call when there is no saved
file, and I'm just loading the last session open (without launching a
script). When I save it and open the autosave of the saved it seems to
fire correctly.
I'm opening an old wound with this and updating a gizmo that needs the
onScriptLoad to build it's internals, so it's really nice to have it
work all the time and not just when opening a script .
Thanks for the sanity check Jep, and thanks for the suggestion, Nathan -
it seems more appropriate now.
JRAB
On 01/18/2014 07:15 PM, Jep Hill wrote:
This is really interesting -- I think I must not fully understand what JRAB is
asking...
When I open a script -- my onScriptLoad callback fires.
If upon opening my script, I elect to go with a "newer modified version of the
script that wasn't saved", i.e. the autosave, the autosave loads and my onScriptLoad
callback fires.
If I load my autosave script directly, my onLoadScript callback fires.
I'm guessing JRAB means something else completely?
Cheers,
Jep_______________________________________________
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
