Wow...Thanks David. I saw 9 responses and thought someone else was chiming in. Its going to take a while for me to read through these and get back to you on it. Your diagram almost reminds me of BSD trees, so if that's the case, can data only be contained by the "ending" nodes? It looks like I'll have to debunk some of my thoughts on how this is working. I was expecting something a little more akin to arrays (whether they be jagged or multidimensional).
Yes, I will be in London...hopefully with something to show of RS2GH as well, but we'll see. Other than S2P I've got training on that Thurs & Fri. Thanks for the new build and the detailed response, Damien On Mar 20, 7:38 am, David Rutten <[email protected]> wrote: > > 6. I can very much see the need to swap paths (path A for path B), > > reverse paths (A,B,C is now C,B,A...but the data within A is the same > > order), split paths into separate streams (A,B,C,D -> A,B | C,D), > > merge paths via index (A,B,C,D with supplied index of 1,3 would merge > > to A, E, C where E is B and C merged together), Append either branches > > to a path structure or data to a branch, Weave Branches. A number of > > those I could see being achievable with a few additional tools, but at > > the expense of taking 2-5 additional components to put together. > > Absolutely. I'm hoping to get the automatic stuff working correct > first, because once you give people a way to circumvent limitations, > they stop complaining :) > > If you have any specific suggestions for path-modifier components, let > me know. Your guess for what's useful is as good as mine. > > > I believe there is one bug that I've found relating to pathing. The > > Tree Branch component won't accept the "two dimensional" paths, even > > though it has a "two-dimensional" structure fed into it. Note: I > > didn't have a problem with this in 6.001 > > I'll look into this. > > ps. Will you be in London for S2F this April? > > -- > David Rutten > [email protected] > Robert McNeel & Associates
