Family Type parameters are the most powerful, and the most restricted type of parameter in Revit. You can't nest them, you can't add them into a family if you haven't already loaded in a family of matching category, you can't control it with a formula, and you can't easily control what they select from or the order that list is in. That's right, turn that lock and throw away the key...
The big issue is the nesting part. The whole point of nesting families is to simplify family creation by taking a complex problem and breaking it up into parts. The whole point of a Family Type parameter is to allow you to take a complex problem and break it up into interchangeable parts. Hmmm. Right hand, meet left hand - now play nice.
But, with all those restrictions what happens if it makes sense to have the FT parameters 2 or 3 levels deep? Well, you have to make that level shared and have to make the FT parameter a Type parameter so you can access it by clicking on the nested family instead of the host. Hold the press... What?
You need it to be an instance parameter? SOL. You need to have it in the host family for scheduling? SOL. Want to control it with a formula? SOL. Anyone want to play Dr. Evil and make a sound every time I want to do something "creative" with a family type parameter? Zip it... Zip it good.
So, #2 on the list is letting us nest those family type parameters several levels deep and tie them to family type parameters in the host families (or control them with a conditional formula, or something!). This takes the meanest parameter on the block an unleashes it on the unsuspecting masses. As for those other problems I mentioned earlier? Those could be resolved by another number on this list...
No comments:
Post a Comment