Hi Rodolfo - I do not know what is expected there - I’ll see what I can find out. @RodolfoSantos - it might be possible to make this work but it might not - the way blocks work, the connection between objects is lost - this is true of any objects connected by History. RH-63012 Dimensions: maintain history in a block
Yesterday, during a live webinar, I had to face a real nightmare because of this ‘unpredictable’ behaviour.
I had decided to propose this strategy during the live webinar because it was working well the day before ?
What I would like to know is whether it’s supposed to work or not ?
In some circumstances, using dimensions is necessary, it is not a secondary feature.
Explaining to the learners that a block-based strategy involving the use of dimensions “may work” is not pedagogically acceptable.
Without further informations, I am simply unable to explain why it is not advisable (although perfectly logical ) to link dimensions to objects stored inside blocks.
Is this related to Rhino 6 or MacOS ?
Is this fixed in Rhino 7 ?
Hi Rodolfo - I think, if I am reading this all correctly, that what you show makes sense if you assume, as is the case, that history relationships are not maintained inside a block.
Hi Rodolfo - What do you mean exactly? How can a dimension be added to a block defintion without being inside it? Do you mean when a block instance is dimensioned, perhaps?
Using a dimensioned Arc ( From Quad to Arc center ) and an Open Curve ( From Crv Mid to a Ref point aligned to Left EndPt )does not provide the same behaviour with the Linear Dimension Object.
History relationship is maintained with the Arc
History relationship is not maintained with the open curve
As the second reference point chosen for the Linear Dimension associated to the open curve is in the air, I would like to ask is this is the wanted behaviour?
You need to snap to geometry, so, yes, that would be the expected behavior.
If you used .x or .y references to place that dimension point, the request is on the list as RH-47854.
-wim