Yet more component requests/alterations... Please

by Matt Gaydon

Mar 30, 2011

Hi David

 

I know you asked others to write there requests in a their own thread so i shall start one too.. as it seems today everyone has requests.

 

1. Pathmapper: Any chance of making it so it does not clean trees automatically as i have sometimes need this data tree path data but need the paths names shorted also is there any chance of having a graft input as well and a preview option?

 

2. Tree Branch: Any chance of changing the path input so it can take wild cards like Tree Split?

 

3. Number of Numbers Count Component: Currently I use a paths and replace branch component workflow to count the number of times a numbers appear in a sorted list though it would be great is we could have a component that does this with out the need to involve paths.

 

4. Value List : Could this have an input option so we could write the list before streaming it into the Value List Component.

 

Thanks for all the great work.

 

Matt

 

  • up

    David Rutten

    Hi Mat,

     

    1. Yeah that's a bug, I'll get it fixed.

     

    2. What would be the difference between Tree Branch and Tree Split then?

     

    3. I'm writing a collection of Set Theory components now and I can see this being one of them. They will only work for simple data types (bools, ints, numbers, strings, points, vectors, colours etc, no curves, breps, circles, meshes). This approach will make it easier to analyse the contents of lists of data, including how often a specific value occurs.

     

    4. I don't think this is a good idea. Changing UI based on the solution can result in all sorts of annoying behaviour where you have to go back and reset a value over an over again and having it erased or changed by a specific solution. 

     

    --

    David Rutten

    david@mcneel.com

    Poprad, Slovakia

    2

    Mar 30, 2011