New Data Matching in 0.9+

Data Matching has changed because:

1. There was a bug under certain conditions and
2. I wanted to make it more economical with regards to path growth.

The new logic is roughly as follows:

First a master input parameter is identified. At the moment, it is the parameter with the longest path length. The amount of paths doesn't matter. Input parameters that have tree access are never master parameters (unless absolutely no other parameter is available) and list parameters have lower priority than item parameters.

In future versions it may become possible to assign a custom input as master. This however is an expert user function and I want to post-pone adding it as long as possible in order for the default behaviour to be tested and improved.

If all input parameters are list parameters, output paths are no longer grown. I.e. the Reverse List component should output the exact same data tree structure as it gets.

The master parameter might not be the parameter with the most branches. It is therefore possible that we run out of defined paths before the component is done computing. If this happens, the last index of the last available path in the master parameter is incremented on each iteration:

Input A = {0;0} {0;1} {0;2}
Input B = {0;1;0}
Output C = {0;1;0} {0;1;1} {0;1;2}

A has a maximum path length of 2, B has a maximum path length of 3, B is therefore the master parameter. However we need three unique output paths since A provides three paths, so {0;1;1} and {0;1;2} are made up on the spot.

It is also no longer possible to apply Shortest List and Cross Reference options to components. Old components that had these options set still work like they did before, but that should be considered legacy support. Instead, there are now three components in the Sets tab, List panel called Cross Reference, Short List and Long List that basically provide the old functionality with a lot of additional flexibility and options.