manually adjusting curve control-points

Hi all! I have a definition in which a user-defined set of points creates a set of curves, which then go through a number of slider-set transformations. I'd like the user (who won't be me) to be able to manually adjust some of the curve control-points partway through the transformations, before going on with the rest of the transformations.

The only way I can see to do this is to bake the curves, manually adjust the control-points, then select the curves and re-input them into the definition. Painful and messy! Can anyone point me towards an easier way? Eg, is there a way to turn on & edit control-points *within* Grasshopper?

Cheers

Replies to This Discussion

Permalink Reply by Danny Boyes on January 31, 2011 at 3:16am

There is a Control Points component that would allow you to gain access to the points, manipulate them and then slot them back into either a Crv or NurbsCrv component.

This would be quite constrictive though as you would need to have the option for every control point already built into the definition with no room for expansion.

Edit: I forgot to cull the original point

Permalink Reply by shinyapple on January 31, 2011 at 5:43am

Thanks for the reply Danny! The control-points component helps a bit, but yeah, the curve reconstruction was what I was hoping to avoid - I have hundreds of curves and reconstructing them means they're no longer in the right branch thingies (sorry, am new to Grasshopper from Rhinoscript - not yet fluent in trees!) It looks like this might be the only way, though, so your diagram will come in handy. :D

Permalink Reply by Danny Boyes on January 31, 2011 at 5:57am

Unless you can define an algorithm, with some coefficients of predefined shape and form with which to manipulate your points, I don't think GH is able to help you directly.

What might help with your problem is to come up with a post selection sorting routine to get them into a set order each time. You could base this on anything from size to location.

Permalink Reply by shinyapple on January 31, 2011 at 6:17am

Oh hmmm, a sorting routine might work... I'm mainly relying on the existing grouping to define colour, but I could also define colour by size I suppose. I'll give it a crack and let you know how I go. Cheers!

(The problem then would be hiding the existing curve set while the user modifies the new set, but I don't think there's an automatic preview-toggle. I need to stop thinking of Rhinoscript methods...!)

Permalink Reply by Santiago Diaz on January 31, 2011 at 9:05pm

If you end up going the scripting route, consider a baking component which reads GUID, and a component with boolean switch that inputs GUID.

Giulio might have some advice:
http://www.giuliopiacentino.com/grasshopper-tools/

Also see for GUID:

http://www.grasshopper3d.com/forum/topics/casting-a-guid-from-a-string

I guess a problem with baking is the what-ifs to think about.

However, baking does offer some goodies. You control the layer baked into, etc.

Also, here's an automatic version of the baking approach:

http://www.grasshopper3d.com/forum/topics/breach-the-bake-gap?id=29...

Not quite what you need, but ideas. Consider a different event to replace the timer approach.

Permalink Reply by shinyapple on January 31, 2011 at 10:46pm

Oooh, thanks Santiago! That automated baking component is exactly what I need. I don't quite understand the re-inputting process yet, but this is a good excuse to get into C#/VB scripting...

RSS