- Math. a quantity or constant whose value varies with the circumstances of its application, as the radius line of a group of concentric circles, which varies with the circle under consideration
- Any constant, with variable values, used as a referent for determining other variables
- Usage objected to by some
- a boundary or limit
- a factor or characteristic: usually used in pl.
Some of these definitions deal with dimensional characteristics pertaining to geometry. Revit is powerful, especially in the Family Editor, where a distance can be given a name and different sets of values grouped by types.
Another favorite example are the view names and numbering. The annotation, view title, list item in the project browser all use the same property and this property can vary in different instances. In teaching I make sure to explain that these different manifestations of view properties are not coordinated. It is the same information.
So as cool as this is did it go far enough? What other opportunities exist?
An opportunity that has struck me lately is naming. What if we names could contain references to other properties?
When you create a new view and set its view phase filter property to "Phase 1" you may next name this view "Exterior View - Phase 1". <record scratch>Data was just entered twice!</record scratch>.
Would it not be better to name the view "Exterior View - %view phase filter%" or "Exterior View - %view phase%"?
How about naming a family type:
"Casement Window - %width% x %Height%" returns-> 'Casement Window - 12" x 24"'
"Door - Has Vision Lite: %VisionIsVisible%" returns -> 'Door - Has Vision Lite: Yes'
What other areas could leverage parameters? Think of the times you have to go back and maintain something. Where does Revit fail you specific to coordination?