I really like the new Rhinodirect.
I have a basic question. Is there a way to reference the value of another constraint in the model?
Can I make one cylinder always be the same radius as another? Can I place a hole half way across a box, dist/2 formula as a constraint?
Full Version: RhinoDirect Constraints
QUOTE (Scott Davidson @ Jul 16 2010, 06:49 AM) 
I really like the new Rhinodirect.
I have a basic question. Is there a way to reference the value of another constraint in the model?
Can I make one cylinder always be the same radius as another? Can I place a hole half way across a box, dist/2 formula as a constraint?
I have a basic question. Is there a way to reference the value of another constraint in the model?
Can I make one cylinder always be the same radius as another? Can I place a hole half way across a box, dist/2 formula as a constraint?
Thank you for your feedback, Scott!
No, now there is no way to reference the value of a constraint. We will definitely implement formulas as a constraint, this is the question of priority. Do you think this feature is crucial for version 1.0?
The equal radius constraint is currently planned for version 0.5.
Good to hear it is on you list of improvements. I hate to be the one to set your priorities.
I find a need to center objects between edges. And I often what to set the same thickness in different distances part. For centering I do think needs to be in early releases.
A more advanced relationships would be evenly spaced objects across a distance would be great to have, but might be able to wait until later.
You might have a better way to solving these issues. I normally would use a =dist/2 or something like that to solve the centering, spacing and thickness relationships.
I find a need to center objects between edges. And I often what to set the same thickness in different distances part. For centering I do think needs to be in early releases.
A more advanced relationships would be evenly spaced objects across a distance would be great to have, but might be able to wait until later.
You might have a better way to solving these issues. I normally would use a =dist/2 or something like that to solve the centering, spacing and thickness relationships.
Thank you for these suggestions Scott!
Basically there are two ways to express center relationships:
1) use formulas (y=x/2),
2) use equal distances and midpoint constraints.
It seems to me that (2) should be simpler for Rhino users, but I would like to know your opinion here.
Basically there are two ways to express center relationships:
1) use formulas (y=x/2),
2) use equal distances and midpoint constraints.
It seems to me that (2) should be simpler for Rhino users, but I would like to know your opinion here.
Yes, I agree that the centering and midpoint constraint is easier. Is is wise to have different style constrints for each releationahip type? Could that lead to too many constraint types?
The formula constraint is more flexible. While it is not as easy initially. If someone understands the concept they can accomplish many different releationships.
It seem to me that the Centering/midpoint is optional. The Formula based approach you are going to need even if you have the midpoint/centering version.
The formula constraint is more flexible. While it is not as easy initially. If someone understands the concept they can accomplish many different releationships.
It seem to me that the Centering/midpoint is optional. The Formula based approach you are going to need even if you have the midpoint/centering version.
Thank you for your opion, Scott.
Finally I think we should implement both these tools (mdpoint/equal constraints and formulas).
Finally I think we should implement both these tools (mdpoint/equal constraints and formulas).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.