In cases like this, I make my group a "grizmo". Export your group as a
gizmo, then edit the text and replace
Gizmo {
with
Group {
Then you can call it with nuke.createNode() but it'll come in as a group.
Handy.
-E
On Thu, Apr 26, 2012 at 6:09 PM, Michael Garrett <[email protected]>wrote:
> This issue is probably pretty common:
>
> For Group nodes with menu.py toolbar entries, currently they are set up to
> come into the dag using nuke.nodePaste() which is ok except for the
> advantage of abstracting their path out by using nuke.createNode().
>
> So when I use nuke.createNode() with a node selected, it places the Group
> at the place it is in that script, which could be miles away from the
> selected node. With nodePaste() it's fine, although recently I ran into an
> issue with a particular Group that won't attach to the selected node when
> pasted.
>
> So, nothing seems perfect here. I could attach a python callback to get
> the createNode() method to place itself correctly but would rather not.
> Anything I'm missing here?
>
> Thanks,
> Michael
>
>
>
> _______________________________________________
> Nuke-python mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
>
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
