Bernard Kwok

Thanks for the details Jerry. This was what I assumed was occurring or desired to be occurring. ( In any case adding `defaultval` into the function arguments will allow for...

Two notes on this: 1. Nested node graphs are disallowed in the editor currently due to lack of support. You'll want to check that the selected nodes do not include...

> I've seen this sporadically as well but wasn't able to reliably reproduce. Do you happen to have repro steps? I've put in a fuller description.

Hi @meshula, This doesn't add any additional metadata to specify the UI ordering. It's just a way to re-order inputs on a nodegraph. Does USD already have separate specifiers for...

Thanks for the explanation about stacking order. To confirm your summary of `childOrder`: - Yes this is construction order but can serve double duty as "interface order" for inputs (not...

@ashwinbhat, @ld-kerley : This is the basic equivalent to the current proposal for glTF which is merging `functional graph` into a `nodedef` to create a `functional nodedef` for lack of...

Would this be a reasonable compromise ? - Just embed the `nodegraph` as a child of a `nodedef` - This would mean we can reuse all the existing `GraphElement` class...

@ld-kerley. @dbsmythe : for the duplicate outputs. The original example tries to collapse both purposes into one port since they are at the same scope. You can specify a default...

Hi @jstone-lucasfilm . This is definitely a possible option, and is listed as an alternative approach above , but I think we'd want to make `nodedef` the one and only...

This would be the layout for nodegraph embedding: ```xml ``` and for source implementation embedding (repeat of Ashwin's example): ```xml ```