You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 6, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 6, 2021. It is now read-only.
My first inclination would be to do something very similar to what core Rhino does. When GripsOn is called for a curve in Rhino, several GripObjects are added to the document. In the context of Grasshopper, I think you would add several AttributedGeometry instances to the ghdoc where the geometry is a Point3d and there is some sort of knowledge that this is a grip referencing a "parent" curve.
I actually do not think this makes much sense in a Grasshopper perspective: Grasshopper does not have grips so that way of thinking is "alien" to it. Is there some method that we could use instead? What are you trying to do?
I understand what you mean about the grips being alien to grasshopper and I agree it doesn't make a lot of sense to have them in GH. I was asking because i wrote a piece of code in python via editPythonScript and was trying to pass it over to GH. The script basically simulates the frei otto wool experiment. The way it was written is that it gets some crvs and then used the grips , grip Locations and distance between each other and attracted the grips modifying the initial crvs. I tried Rhinocommon but Im not very proficient with it and got lost..If you have any idea or way around it let me know.
@philpidis if you were able to show me a sample of what you were doing with grips, it should be possible to either rewrite the code in RhinoCommon or use RhinoScript methods to delete these curves and recreate them with the right control points.
Activity
sbaer commentedon Nov 2, 2011
My first inclination would be to do something very similar to what core Rhino does. When GripsOn is called for a curve in Rhino, several GripObjects are added to the document. In the context of Grasshopper, I think you would add several AttributedGeometry instances to the ghdoc where the geometry is a Point3d and there is some sort of knowledge that this is a grip referencing a "parent" curve.
Filippos-Filippidis commentedon Feb 17, 2016
Hi to both!
Is there any update on the Grips method?
Thanks
piac commentedon Feb 17, 2016
Hi Phil,
I actually do not think this makes much sense in a Grasshopper perspective: Grasshopper does not have grips so that way of thinking is "alien" to it. Is there some method that we could use instead? What are you trying to do?
Thanks,
Giulio
Filippos-Filippidis commentedon Feb 17, 2016
Hi Giulio.
I understand what you mean about the grips being alien to grasshopper and I agree it doesn't make a lot of sense to have them in GH. I was asking because i wrote a piece of code in python via editPythonScript and was trying to pass it over to GH. The script basically simulates the frei otto wool experiment. The way it was written is that it gets some crvs and then used the grips , grip Locations and distance between each other and attracted the grips modifying the initial crvs. I tried Rhinocommon but Im not very proficient with it and got lost..If you have any idea or way around it let me know.
Thanks for the fast reply,
Best,
phil
piac commentedon Feb 22, 2016
@philpidis if you were able to show me a sample of what you were doing with grips, it should be possible to either rewrite the code in RhinoCommon or use RhinoScript methods to delete these curves and recreate them with the right control points.
Filippos-Filippidis commentedon May 30, 2016
@piac
It worked with Rhinocommon!
thanks