> 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
