SubGraphScope

Remarks

⚠ The enclosing scope and not the sub-graph being expanded. A value written on a sub-graph node's port is written where the node is, so what it may read is the containing graph's parameters with the containing expansion's overrides — which is the join that made #1074 a seam rather than a branch: a compound two levels down is neither the author's graph nor a published graph's declared defaults, and only this walk knows which one it is.

Fields and properties (4)

• public string Type

  The node-type path of the graph the sub-graph node is written in, or the empty string for the author's own graph. It is what a front end looks a parameter list up by.

• public int Expansion

  Which expansion that graph is — Expansion's number — or 0 for the author's own.

• public IReadOnlyDictionary<string, string> Settings

  What the sub-graph node that graph came out of was given, or empty for the author's own graph. Two instances of one published graph are two of these.

• public NodeId Blame

  The node a complaint about a value resolved in this scope should name: the outermost sub-graph node, which is the one the author has on their canvas.

Methods (1)

• public SubGraphScope(string Type, int Expansion, IReadOnlyDictionary<string, string> Settings, NodeId Blame)

  Which graph a sub-graph node was written in, and what that graph's instance was given.

Used by (3)

• FlattenerVixen.Editor.NodeGraph
• ISubGraphValuesVixen.Editor.NodeGraph
• TextureGraphCompilerVixen.Editor.TextureGraph