Either I haven’t understood how “Propagate ancestor” from Treesloth works, or it just fails for some reason in this case.
Custom propagate ancestors.gh (828.2 KB)
Propagate Ancestors needs there to be a common path between the two data trees you want to integrate:
Hope this helps!
The use case in this thread isn’t really what I built it for…it’s definitely a very simple example, and for sure in this instance your solution is more suitable. PA is built for for more complex data relationships…say, for example, you have three surfaces that you’ve subdivided, and then built upon the subdivided elements…maybe even subdivided them, etc. And then you want all of those subdivided elements to tie back to the three original surfaces while retaining the more complex data structure:
1 Like
Hi Dave,
I think this is why I had a hard time understanding what this component did : in many cases, you don’t have a common branch number !
You might want to add this valueable info here.
I got it to work indeed, using the path mapper :
“Longest list” seems restricted to very basic cases.
It doesn’t work here, but PA does :
Longest List Vs PA.gh (16.2 KB)
I see that “Propagate ancestors” works with multiple shared root paths…