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
where the bottom part is a separate solid, and one must create a top part which must be in syc with some projected geometry. The most natural way is to create some reference dimensions, name them and use in an expression like in below example:
Unfortunately currently it is not allowed.
Possible reason: assumed cyclic dependency.
The workarounds are rather clumsy and involve creating multiple "helper sketches".
Could You please change this "no go" into a warning? I know that it is hard to check if there is a true cyclic dependency (in this case it is not) in case of geometry and I know that cyclic dependencies may confuse the algorithm. As a user I would be glad to be warned but still allowed to take the risk.
By the way, I am curious for what the reference dimensions are meant to be used then, if not to drive a geometry? For me this workflow I have shown above is most natural way of using them. I used this method in Autodesk Inventor a lot with, of course, crazy things happening when a true cycle was created.
The text was updated successfully, but these errors were encountered:
Assuming following project:
where the bottom part is a separate solid, and one must create a top part which must be in syc with some projected geometry. The most natural way is to create some reference dimensions, name them and use in an expression like in below example:
Unfortunately currently it is not allowed.
Possible reason: assumed cyclic dependency.
The workarounds are rather clumsy and involve creating multiple "helper sketches".
Could You please change this "no go" into a warning? I know that it is hard to check if there is a true cyclic dependency (in this case it is not) in case of geometry and I know that cyclic dependencies may confuse the algorithm. As a user I would be glad to be warned but still allowed to take the risk.
By the way, I am curious for what the reference dimensions are meant to be used then, if not to drive a geometry? For me this workflow I have shown above is most natural way of using them. I used this method in Autodesk Inventor a lot with, of course, crazy things happening when a true cycle was created.
The text was updated successfully, but these errors were encountered: