David Lai
David Lai
I have refactored to adopt `"assetOptions"`, but noted that the `config-1.0` schema also need to be updated as well since "assetOptions" is a new property in project config. Or should...
> Or should we make a config-1.1 schema ? Or config-2.0 ? I will add `config-1.1`, since it's a minor change.
> > Or should we make a config-1.1 schema ? Or config-2.0 ? > > I will add `config-1.1`, since it's a minor change. I think the last comment I...
Sorry for late reply :sweat_smile: > I dont know how stable cloning is in the later versions but in Nuke 9 is was definitely very unstable and could corrupt the...
> Instead of cloning we could also have an ID similar to how @BigRoy and Colorbleed tracks nodes in Maya. We could continue with using a group to store the...
Okay, here is the code for updating *referenced* nodes. It seems workable ! ```python import contextlib import nuke def get_copies(source): """Return nodes that has same 'avalonId' as `source`""" def get_id(node):...
Has anyone tried this before ? I am giving a try on this feature, and implemented a simple dependency data collect mechanism in my config, pretty rough right now. The...
Just adding notes. * The `api.create` was originally from #291. * Only one last `instance` is returned from `api.create` no matter how many plugin been processed.
Yeah, if we also pipe logs into a log file, or just keeping them in memory, could do !
> Could this also allow to expand and see the full log history in something like Maya's script editor? About full log history, which one would be better for this...