I'm creating a detail item family that has type of wildly different sizes per type. The visibility parameter controls what you can see but it does not affect what your mouse will pre-select when you hover over it.
The only workaround I've found it creating another detail item to nest into the main and control the visibility for the element in the family. This hides the nested family in types you don't want to see it in AND makes it so that it's linework is not select-able. The problem with this method is that it adds nesting to the family, which normally wouldn't be that hard except I'm already nesting quite a bit on these detail items and it affects the way a Dynamo script I have works.
Right now I have this structure:
The Dynamo basically breaks the main family into linework and the part family so that people can make changes that are specific to projects. If I were to use the method described above to fix the issue with the main family I would have to add additional nesting between the Main(1) and the part family(A) which would break the Dynamo script or force me to make it much more complex.
...so the long and short of this to prevent users from messing with the Family's settings?
This is what I've done and what I'm trying to achieve. https://autode.sk/3eCa65a
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.