Grasshopper 0.9.0055 available for download

Replies to This Discussion

Permalink Reply by Danny Boyes on May 16, 2013 at 10:21am

The main reason I use False is for [Shift List] S = -1 in order to get rid of the last Item other than that it doesn't crop up  

Permalink Reply by Vicente Soler on May 16, 2013 at 12:24pm

If you want to get rid of the last item doesn't it make more sense to use the Cull Index component?

With the new default you just have to input -1 as well.

Permalink Reply by Steve Lewis on May 16, 2013 at 5:49pm

interesting, never used negative shift values, typically i revers the input list, shift, then  reverse output list

Permalink Reply by Alessandro Ronfini on May 16, 2013 at 10:27am

Actually yes, and I often use it to shift entire branches too.
But i'm working on a peculiar geometry..

Permalink Reply by Chris Landau on May 16, 2013 at 11:36am

Me as well. 9 times out of 10 I am stripping off the end branches. Is there a more canonical way to do this?

Permalink Reply by David Rutten on May 16, 2013 at 11:58am

I almost always use wrap=true index=-1 to get the last item. The change was requested by people who do the same I think.

There would be a more canonical way of doing it, basically I could keep a record of the N most recent values and pick a default that was the majority amongst those.

That would be both customizable without adding any nasty preferences UI. It would however make it somewhat unpredictable.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Vicente Soler on May 16, 2013 at 12:56pm

I think this would be confusing, not knowing the default when sharing definitions, screenshots and so on.

I would leave true as default (well, if I got my way the warp inputs would be removed altogether) and to strip off the end values use something like cull index, split list, sub-list, etc.

 

The replace items component still has the default as false.

also, split list component doesn't support wrapping.

Permalink Reply by Alessandro Ronfini on May 16, 2013 at 1:03pm

I admit logic wants true to be the default... 

And I agree an unpredictable result will not be fun, so it's easier to get used to the new default!

Permalink Reply by gotjosh on May 17, 2013 at 5:36am

you could consider making pop and unshift fxs that do the traditional array operations...

Permalink Reply by Marc Syp on June 19, 2013 at 5:47pm

Incidentally, for last item I've always used List Item with default index set to 0 and  a reverse list modifier on the list input.  Super quick, and easy to explain to beginners.

I use T for several operations, but the majority is F for me as well.  The topology of things that I work with is rarely periodic.  Curtain walls, structural grids, test grids, analysis vectos, modules, etc, they tend to be arrayed in groups with finite beginnings and endings.  That makes wrapping very rare.  

I think conforming to the use case for finding the last number in a list is too narrowly defining the use of that component, especially when the simple task is easily accomplished in another rational and efficient way...

Permalink Reply by Vicente Soler on June 19, 2013 at 6:55pm

Reversing a list consumes resources. If you just want to retrieve the last item using index -1 is more efficient.

 

When you say you use false the majority of times, you mean that in the majority of the cases you use a component with a wrapping input if you set it as true it will fail?

Permalink Reply by Vicente Soler on May 16, 2013 at 12:27pm

100% of the times I use wrap true (or it doesn't matter) so default as true wins by 0.1% :P

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page