This compares a pair of components. It first identifies nodes that are unique to either of the two components.
Then for the nodes that exist in both components, it identifies differences in parameters, flags, input wiring, hierarchy wiring, language, tags and comments.
For nodes that are in both components, it checks the operator family and type, and reports if they are different.
It reports on DATs whose contents differ (Text, Table and the Execute DATs, and DATs that are locked).
Using âOnly in Component 1â and âOnly in Component 2â, it shows nodes that exist in one component but not the other.
If you turn on the parameters âFlagsâ, âParametersâ etc, it will compare the Flags, Parameters etc of nodes that are in both components, showing the differences in columns âvalue1â and âvalue2â.
âWiringâ reports on the input wires of nodes including components, as well as hierarchy (bottom to top) connections of 3d object components and panel components.
âMiscellaneousâ look at tags, comments and mis-matched node types.
The âCosmeticsâ option checks for things that donât matter in the function of the node, like viewer state and node position in the network.
The two built-in test components illustrate the various comparisons.
The component outputs the DAT you see in the viewer.
If you turn on âRemove Unused Colsâ, it will make the table simpler. For example, it will not display/output column âonlyInComp2â if the parameter âOnly in Component 2â is off, etc.
I donât know how many times Iâve wanted to know what Iâve changed between two versions of a component. This gives a good comparison.
compareComp doesnât check everything yet - you can add what you feel is necessary within this structure. Not implemented is locked CHOPs or TOPs, and it doesnât co-relate a node that was renamed. Nonetheless, the results are illuminating.
uploaded version 5 on June 18 2018
THIS COMPONENT IS IN THE TOOLS PAGE OF THE PALETTE OF THE OFFICIAL BUILDS AS OF JUNE 15, 2018.
compareComp.5.tox (14 KB)