A Record Component Wish

Replies to This Discussion

Permalink Reply by David Rutten on July 16, 2014 at 6:49am

I assume this would be a Boolean Input. If you supply more than one boolean, what should the behaviour be like?

--

David Rutten

david@mcneel.com

Permalink Reply by Danny Boyes on July 16, 2014 at 8:15am

For instance (hypothetically speaking) if a maximum value or a maximum number was reached the record for each branch could be cleared only if it's own criteria was met.

Permalink Reply by Mateusz Zwierzycki on July 16, 2014 at 8:35am

Just make it reject the second connection... 

Permalink Reply by David Rutten on July 16, 2014 at 8:52am

How is that better than looking if any of the supplied booleans is TRUE?

--

David Rutten

david@mcneel.com

Permalink Reply by Mateusz Zwierzycki on July 16, 2014 at 8:59am

Well, it may be better in terms of UI clarity (or not, since it's a new kind of behavior).

Another solution would be to display an error when more than one value is provided - just like stream gate/stream filter does. User can always create his/her own switching logic with boolean operators.

Permalink Reply by David Rutten on July 16, 2014 at 9:42am

I think I prefer the warning route, there are already some components which require no more than a single value in an input, but it always strikes me as awkward.

--

David Rutten

david@mcneel.com