Grasshopper

algorithmic modeling for Rhino

Hi David,

 

It seems like there is a bug in the Addition Component as it retuns the input number if the other number is Null when all other components return null values if one input is null.

 

Also is the split tree component now meant to be returning nulls now for all the values that have been put in the other list??

 

Thanks

Matt

 

 

Views: 374

Replies to This Discussion

Hi Matt,

both of those things are by design. Since Addition has variable inputs, only those values that have actually been specified will get added together. Nulls are ignored.

Split Tree I think always kept nulls in those places that didn't pass any of the filters.  This is vital in case you want to recombine the two trees again later and have the order of items be intact.

--

David Rutten

david@mcneel.com

Hi David,

I did a few sceen Captures showing why i questioned it.. Whould it not be better is it returned a null if only a single value was input?

And this is a code where tree split seems to be running the old logic Which meant you only have the tree's the selected tree in the list wih no nulls for the other trees. I can understand why the new idea maybe usefull though it would be great to have boh if possible so you don't have to add a clean tree if you don't want all the nulls. Also how would you merge the trees with nulls back togethe, i tried a few options but only way i could do it was clean tree and use replace nulls in the other tree.Thanks

Matt

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service