This also happens if you create a ReadGeo node via the script-command entry -
the alembic reader doesn't get initialized properly.
I haven't looked at it yet but I'd take a peek at the python code that's bound
to the 'ReadGeo' menu item - there's clearly something additional being done
after the file browser is closed.
-jonathan
On Jul 16, 2013, at 5:48 PM, nukepython.cali...@neverbox.com wrote:
> My first attempt to create a ReadGeo node looked like this:
>
> n = nuke.createNode('ReadGeo2')
> n['file'].setValue('alembicFile.abc')
>
> However, when I set the file knob, I would get a popup dialog that would ask
> the user if they wanted to "Create all-in-one node" or "Create parents as
> separate nodes".
>
> Wishing to avoid this pop-up dialog, I then tried:
>
> nuke.createNode('ReadGeo2', 'file {alembicFile.abc}')
>
> This would, indeed avoid the dialog... but it seems the dialog is essential,
> as the ReadGeo node would not show all the nodes contained in my alembic file
> (it would only show one of four objects in a hierarchical structure).
>
> So... does anyone know what exactly this popup dialog is doing, or how to
> recreate it's effects without requiring user interaction?
>
> Thanks,
> - Paul
> _______________________________________________
> 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
