algorithmic modeling for Rhino
Hi Atsuo, i think this would be a big loss to the functionality of the listItem component, because i sometimes like to give it the indexes parametrically, wait another month until andrew heuman gifts us with the announced grasshopper goodies. There will be one component that allows you to feed a list into a component similar to the valueList component and then choose one specific item out of there. Cheers Alex
Hi Alex,
I am not sure it's big loss or not, but now I found that I can use cluster component for multiple List index out. So it's just small issue for me now.
Thanks!
It's actually a good idea to also output the previous and next items. Maybe hide it behind a variable parameter ZUI...
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Your right, i admit i didn't think of that, guess that would be useful. But why get rid of the index input?
I wouldn't. Without an index input there'd be no concept of previous and next either.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
This is how the new List Item component works: By default it looks and works the same as the existing one. But you can add and remove outputs to/from the top and bottom:
Resulting in:
I thought I'd keep it simple and not allow custom offsets. So if you want i+2 you'll also get i+1 whether you need it or not.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Awesome David! this gets a lot listshifting functionality out of the listitem comp. What happens if i expand to +2 and the collapse the +1 in zui? Does +2 stay or does it default back to +1?
You can only remove the outermost parameters. So if there's a +2, you won't be able to remove the +1 (as the image on the top shows).
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Hi David,
This is exactly what I wanted.
I am little tired each time add index and get result.
Thanks.
oh i see, (or should have seen...) still very cool though, as shifting by 1 or -1 already does a lot for me. Really looking forward for the next build, cant wait for the patch component!
Great!
If I need wrap around on the i input, but not on the previous and next outputs, I would have to solve it another way (i.e. i mod len), right?
Yes, if you want different wrapping logic for the different outputs you'll have to use multiple ListItem components.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by