Node: Static and dynamic output type for extended nodes #22590
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Now
NodeMaterial
support static and dynamicgenerate
output type for extended nodes, therefore is not more necessary to convert allgenerate snippet
for a different output in an extendedNode
, it simplifies the code for creation of futuresNodes
besides being backwards compatibly.How a simple code design change can make a difference: Only here, we reduce more than 100 lines of code...
Usage
Static
Allow that
Node class
convert the default snippet generated for the requested output.Dynamic
Allow that the
Node
find the better snippet for the requested output.This contribution is funded by Google via Igalia.