AUTOFILL Tree Structure for pathmapper??

Is there a way to read a tree structure and use it to autofill the path-mapper?

i.e. {A;B;C} > {A}

or {A;B;C;D;E;F} > {A}

(Obv after simplification)

Having multiple variables in terms of geometry coming into my definition. It would be good to reduce various paths down to simply one branch structure without re-programming the path mapper for different configurations.

Im sure this is a simple trick?

Replies to This Discussion

Permalink Reply by David Rutten on January 23, 2017 at 6:49am

Sure, just right click and pick one of the standard mappings provided. It'll adapt it to whatever tree is currently active.

Permalink Reply by Jonathan Sheridan on January 23, 2017 at 6:51am

Nice

Permalink Reply by Joseph Oster on January 23, 2017 at 7:58am

Yeah but... this doesn't respond to changes in the input tree structure. Having to right-click and recreate the flatten mapping is a form of reprogramming. Maybe Jonathan is looking for 'Path Mapper' syntax that works regardless of how many levels are input? (Similar to the effect of using 'Simplify' before passing the data tree to 'Path Mapper') So easy to forget this stuff.

Permalink Reply by Jonathan Sheridan on March 2, 2017 at 2:01am

Yes Joseph you've read it right. I have since tried Davids Path mapper and it does'nt update to changes.

David can this be updated every time the algorithm is re-run? I think its quite a big thing as one can then handle complex assemblies of geometry without having to re group after operands make changes to sub components.

Hope you can hook me up with this one?

Permalink Reply by Matt Gaydon on March 2, 2017 at 3:01am