To elaborate:
http://groups.google.com/group/grasshopper3d/web/grasshopper_stucture_tree_icons.png
The above network divides two curves into 6 points each. Thus, the
output consists of 2 lists, each N=6.
Then, all those points are 'extruded' into lines which are then again
divided. Now, you can see that the points from the final division
'know' they belong to a certain line segment (the second index in the
path space) AND also that they were created from different original
curves (the first index in the path space). Hence: "path {0;2}"
means "the third line segment from the first curve" and "path {1;5}"
means "the sixth line segment from the second curve".
There are still bugs in this new system, and since it affects
EVERYTHING, I'm not going to release it until I at least fix the ones
I found so far. But I'm still finding them faster than I can fix 'em.
--
David Rutten
[email protected]
Robert McNeel & Associates
On Feb 24, 5:35 pm, David Rutten <[email protected]> wrote:
> All parameters are branching parameters now. That icon is just
> something which allows you to explore the branching structure. It
> tells you how many branches there are, how many items they contain and
> what their path space is.
>
> What do you think I've been doing these past 3 months?! :)
>
> --
> David Rutten
> [email protected]
> Robert McNeel & Associates
>
> On Feb 24, 5:25 pm, Rchitekt <[email protected]> wrote:
>
> > Sorry, I meant upper right hand corner. The icon that looks like a
> > "tree".
> > -Andy
>
> > On Feb 24, 8:24 am, Rchitekt <[email protected]> wrote:
>
> > > Do my eyes deceive me, or is there a new branching component in the
> > > upper left corner of your component list? If so, that's going to be
> > > cool. Does that mean you've got looping in the next version?
> > > -Andy
>
> > > On Feb 24, 8:18 am, Rchitekt <[email protected]> wrote:
>
> > > > I agree. That's going to help alot. Can't wait for the new version.
> > > > -Andy
>
> > > > On Feb 24, 8:12 am, Andrew <[email protected]> wrote:
>
> > > > > Yes, that will be a great addition! Thanks David!
>
> > > > > Andrew
>
> > > > > On Feb 23, 7:55 am, fraguada <[email protected]> wrote:
>
> > > > > > That receiver makes me happy...well done sir!
> > > > > > Luis
>
> > > > > > On Feb 23, 3:38 pm, David Rutten <[email protected]> wrote:
>
> > > > > > > I added a receiver object today. The connections on the input
> > > > > > > side are
> > > > > > > either never drawn, always drawn or only drawn when the object is
> > > > > > > selected (default).
>
> > > > > > >http://groups.google.com/group/grasshopper3d/web/Receiver.jpg
>
> > > > > > > It's actually just a Generic Data Parameter in disguise, but I can
> > > > > > > tweak the display even more if you want it to be smaller or
> > > > > > > larger or
> > > > > > > bluer or distinct or...
>
> > > > > > > --
> > > > > > > David Rutten
> > > > > > > [email protected]
> > > > > > > Robert McNeel & Associates
>
> > > > > > > On Feb 22, 6:16 pm, David Rutten <[email protected]> wrote:
>
> > > > > > > > Hi Marc,
>
> > > > > > > > > 1) Working, separately editable/instanceable/properly
> > > > > > > > > previewable
> > > > > > > > > clusters (I know, I know, it's complicated and you're working
> > > > > > > > > on it!!)
> > > > > > > > > 2) A Send/Receive data component ... I'm assuming
> > > > > > > > > this is a fairly simple thing to implement? It would be a
> > > > > > > > > godsend.
>
> > > > > > > > It would be fairly simple to implement. And I can see the huge
> > > > > > > > organisational benefits.
> > > > > > > > Maybe I can slip one of these in before the next version is
> > > > > > > > released.
> > > > > > > > But since I kinda-sorta promised Bob it would be next week, I'm
> > > > > > > > not
> > > > > > > > sure if I can make that.
>
> > > > > > > > > 3) Previewed geometry "always on top." ... Is there an easy
> > > > > > > > > fix to make
> > > > > > > > > the current preview component ALWAYS show in green over the
> > > > > > > > > top of all
> > > > > > > > > red previews?
>
> > > > > > > > I don't know. I'll have to discuss this with our main OpenGL
> > > > > > > > guy, and
> > > > > > > > then hope that it's possible in DotNET as well.
> > > > > > > > It would incidentally be fairly easy to add Stored Preview
> > > > > > > > States to
> > > > > > > > Grasshopper. Does that sound like something you might still use
> > > > > > > > if the
> > > > > > > > other option would also be available?
>
> > > > > > > > > 4) Gates and switches. Again, I use Max/MSP as a model... but
> > > > > > > > > having
> > > > > > > > > controllable gates allows you to set up testing scenarios and
> > > > > > > > > quickly
> > > > > > > > > switch between states. Also has implications for conditional
> > > > > > > > > data
> > > > > > > > > manipulation.
>
> > > > > > > > There are some gates and merge components available now, but we
> > > > > > > > need a
> > > > > > > > lot more. Feel free to post some detailed descriptions of the
> > > > > > > > functionality you're looking for.
>
> > > > > > > > > 5) Undo. If only to save myself from those moments when the
> > > > > > > > > mouse
> > > > > > > > > slips and I connect to the wrong input, therefore initiating
> > > > > > > > > the "What
> > > > > > > > > was this connected to?" adventure.
>
> > > > > > > > Undo is about half finished (has been for months, haven't had
> > > > > > > > the
> > > > > > > > courage to tackle the second half). It should be available
> > > > > > > > sometime
> > > > > > > > soon. But not very soon.
>
> > > > > > > > --
> > > > > > > > David Rutten
> > > > > > > > [email protected]
> > > > > > > > Robert McNeel & Associates
