I dont think this is a 'correction' (or a bug even though submitted) but just
the intended difference between groups and gizmos - groups can be changed
dynamically, Gizmos cant.
There are advantages and disadvantages to both, but at least you have both.
With Gizmos you can dynamically update all scripts* - good for bug fixes or bad
for major changes. (see below)
Groups you cant.
Groups you can dynamically change internal workings
Gizmos you cant
etc...
Gizmos only save the knobs
Groups save all internal workings
you can make gizmos into groups
groups er... um...
* you can version the gizmo ie myGizmo1, myGizmo2 etc and update the menu.py to
suit and this will stop it dynamically updating all scripts, only when new
nodes
are created. Keep old versions online but hidden for backwards compatability
and
add the line 'name myGizmo' to stop the name changing to myGizmo2_1 in the DAG.
- this is my preferred method for allowing gizmo development without damaging
older scripts.
Howard
________________________________
From: Bertrand Lempereur <[email protected]>
To: Nuke Python discussion <[email protected]>
Sent: Thu, 14 April, 2011 10:08:18
Subject: Re: [Nuke-python] Dynamic node creation inside a Gizmo
Works fine as Group,
Thanks for the tips, hope this will be corrected!
Regards,
2011/4/13 Ivan Busquets <[email protected]>
If I remember correctly from an older post, this was a regression in 6.1, and
has been logged as a bug.
>The same approach used to work in 6.0.
>
>While this is broken, I believe Ben's suggestion is the best way to avoid this
>issue. Just turn your gizmo into a "grouzmo" by editing the .gizmo file as he
>mentioned, which will allow you to call the node the same way you would with a
>gizmo, but create a group instead, meaning everything inside it will be saved
>with the script, and you avoid the need for an onCreate or onScriptLoad
>callback
>altogether.
>
>
>
>
>On Wed, Apr 13, 2011 at 4:49 AM, Ben Dickson <[email protected]> wrote:
>
>The usual solution to dynamic gizmo'y nodes is to use a group, then the
>>PyScript button (or callback etc) which clears and rebuilds the content
>>
>>You can export your Group as a gizmo, as usual, then edit the file in a
>>text editor, replacing the first "Gizmo {" with "Group {"
>>
>>Avoids having to worry about rebuilding the contents on script load,
>>things like losing the input connections..
>>
>>
>>Bertrand Lempereur wrote:
>>> I have been looking for dynamic node creation "Shake like" inside a
>>> Gizmo and i find a post in archive about a Gizmo called TimeMachine. I
>>> study it and begin to create some Gizmo with this method. But after
>>> digging in a little, i see that such node don't keep the input
>>> connection when you reload your script or when you duplicate a group of
>>> node with such node in.
>>> Any idea on how to solve this?
>>>
>>> Regards,
>>>
>>> Bertrand Lempereur
>>> TD at MikrosImage
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Nuke-python mailing list
>>> [email protected]
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>>
>>--
>>ben dickson
>>2D TD | [email protected]
>>rising sun pictures | www.rsp.com.au
>>_______________________________________________
>>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
>
>
--
Bertrand Lempereur
TD at Mikros Image_______________________________________________
Nuke-python mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
