Continued developer absence

Replies to This Discussion

Permalink Reply by Daniel Xiong on July 30, 2009 at 7:23am

Thx David,
but I don't understand you well. Actually if i don't flatten the input and just unconnect x, the output will be different. I don't know the difference between connecting x and unconnecting x since x should be ignored in the VB Script.
I jump from rhinoscript to VB.NET, so if my question is too silly for you and you need to spend too much time to explain to me, please feel free to ignore that.
Looking forward the next build!

Permalink Reply by David Rutten on July 30, 2009 at 8:48am

Hi Daniel,

regardless of whether you use the x input or not, the VB component is still called once for every value that you supply (unless x is a List parameter, in which case it is called once for every list you supply), so the behaviour of the component IS affected by it's inputs.

All input and floating parameters in newer versions have a Flatten option (look in the parameter context menu). This function will merge all the lists into a single big one. If I flatten both x and y, the output of the component changes, meaning that probably x and y are not 'matched up' correctly.

Permalink Reply by Daniel Xiong on July 30, 2009 at 10:10am

Thx for your reply:)
I am starting to get some clue of it.

Permalink Reply by Tobias Schwinn on July 30, 2009 at 6:38am

How about the bitmap parameter component?

Permalink Reply by David Rutten on July 30, 2009 at 8:48am

It's in there.

Permalink Reply by Tobias Schwinn on July 30, 2009 at 7:42pm

Great!

Permalink Reply by Rafi on July 30, 2009 at 10:44am

Hallo David,
Is it maybe possible to create a function fore add length to a curve and likewise surface.
A further function would be usable unfolding straight lofted surface.

thanks Rafi

Permalink Reply by Marc Syp on July 30, 2009 at 8:26pm

Great to hear you're working on a new release ASAP. I've read through the various requests, and one major one that hasn't been mentioned yet: the sweep components. As many people have noted, they are very very finicky, and only seem to work in rare cases with a combination of finagling and voodoo. Sweeping a profile at some distance from a curve seems to be particularly a problem. If you could take a look at those components, that would be fantastic.

Thanks,
Marc

Permalink Reply by Marc Syp on July 30, 2009 at 9:48pm

Also a simple request regarding receivers... I have made the mistake of deleting important components in a definition because I didn't realize that they were connected to receivers downstream. With no undo, this can be a real nightmare...

Can you make it visible that a component is connected to a receiver when it is highlighted? I simple green dashed line (of whatever data type) that fades out quickly would be helpful.

Basically the same way it is visible what a receiver is connected to when you select the receiver itself, you should be able to see any connected receivers when selecting the components themselves...

Thanks,
Marc

Permalink Reply by David Rutten on July 31, 2009 at 2:19am

Hah! Serves you people right for wanting invisible connections!

I've been working on the undo system for a while now, it's nearly there (big project).

Permalink Reply by David Rutten on July 31, 2009 at 2:18am

I agree. But I need to talk to the guys in Seattle about Sweep. They've been working on more robust algorithms and I have no idea how all that magic goo is supposed to work. I'll be meeting with them in a few short weeks, hopefully we can clear up all this mess and also add some Network Surfacing routines.

Permalink Reply by Elizabeth Tweedale on August 17, 2009 at 7:47am

Wish there was an easier way to draw boxes within Grasshopper instead of loading them from Rhino.

• ‹ Previous
• 1
• …
• 4
• 5
• 6
• 7
• Next ›
• Page