How can you change the place of a parameter in a Family ?
When you add a new parameter it's imposseble to move it up or down, also with exicting parameters
Second question
How can you hide parameters in a Family ?
How can you change the place of a parameter in a Family?
- Make a number of parameters of the "Type of Parameter :" you need, name them A, B, C, etc. Load the family into a project and place an instance. See what the order of parameters is in the family's properties. Go back into the family editer and make the parameters into what you want according to where you want to see them.
How can you hide parameters in a Family?
- Can't hide them but you can "Group parameter under :" something like Other which will appear farther down the list in the family's properties window.
@Anonymous wrote:"How can you change the place of a parameter in a Family ?"
The Parameters are ordered alphabetically, but only by the original name of the Parameter, which means that renaming it does NOT change the order. Recreating it does.
If you create the parameters "A", "B", "D" and then rename them, they will remain in that order. Say we change them to "B", "A", "BB". If we create a new parameter "C", then it will be ordered based on the original names ("A", "B", "C") so it will now appear in the order "B", "A", "C", "BB".
There may be a third-party Add-In that can re-sort parameters - try searching the Revit forums.
@Anonymous wrote:"How can you hide parameters in a Family ?"
>>This<< is a link that was posted in the past which explains a method to hide Shared Parameters.
Traditionally, I have hidden extraneous parameters by means of embedding. I build the family with all necessary parametrics and then load it into a new family of the same Category. Then I create parameters only for the needed 'controls' and link them to the parameters in the embedded family. See attached example (Revit 2012).
@Anonymous wrote:"if this is the solution Autodesk has some work to do"
Welcome to Revit! There is a staggering number of problems that are solved by impractical work-arounds in this program, many of which are basic issues that shouldn't have been an issue in the first place. However, the program does have it's strengths and it is powerful, and *some* of these problems are being addressed as it evolves.
Can't find what you're looking for? Ask the community or share your knowledge.