Parameter scope inconsistencies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
We really like using the combination of a Canvas, User Parameters as well as renamed dimensions.
Our canvas has a front view and a side view. We effectively trace over the front view to make faces. Lines drawn over the side view are given dimensions, which we give meaningful names. These are used to extrude faces drawn over the front view.
PROBLEM #1
When giving a name to a dimension, it must not match any other parameter anywhere in entire document. But, you can only use that parameter locally. This is annoying and forces us to make unnecessarily long parameter names (we changed "depth" to "motor_depth"). Given that you can't use a named dimension in another component, what is the point in letting that component dictate what names we can use? Idiots will continue to name things poorly or not at all, there is only so much you can do to keep them out of trouble, so please don't punish those that are well-organized
PROBLEM#2
We cannot even use named dimensions from one sketch in another sketch within the same component. We wanted to have a sketch named Dimensions, but instead had to put a lot of stuff in just one sketch.
PROBLEM#3
Our document contains two child components that are not nested. When attempting to use parameters to set dimensions in the second component, only User Parameters appear. The dimensions we renamed in a sketch within the second component never show up.
SUMMARY
The obvious workaround is that we will have to type in some dimensions. Fusion 360 is still an awesome tool.
As software engineers, this feels to us like confusion about what the scope of sketches and parameters should be. We vote for the only restriction being that parameters can only be used in their own component. However, (and we tried this) we would like to be able to reference them in an object-oriented sense, i.e., component1.paramX, etc.