jsteinhauer
2015-04-30, 12:11 AM
Hello All,
We are having an internal debate on modifications to our standard door families. We already have a parameter within our doors that control the swing angle. This allow us to change our graphics in plan. Currently, this is a Type parameter. But there are those whom would like to see it changed to in instance parameter, for reasons of 'Flexibility'. There are Pro's & Con's for each. I was hoping to get a read from you nice folks on AUGI for your thoughts. Mine are listed below.
Thank you in advance,
Jeff S.
Pro's for Instance
Less family types
Less clicks to change angle
Less training
Con's for Instance
'Select All Instance' is based on type, and if the values are different, the parameter be empty
Harder to track down incorrect setting.
Adds more data to the project file than Type parameters, all be it minimally
Could lead to lazy modeling (if door swings collide, adjusting swing angle will hide issues)
Untested assumption: If parameter is modified, additional placements may take on incorrect values
Pro's for Type
Easier to identify and fix multiple instances of the doors
Naming convention would contain non-standard angles (not 90)
Harder for end users to change
Should be a limited number of angles (45, 90, 170), 90 being the baseline standard.
Con's of Type
Longer Type Names
More training maybe required
Limits 'Flexibility'
We are having an internal debate on modifications to our standard door families. We already have a parameter within our doors that control the swing angle. This allow us to change our graphics in plan. Currently, this is a Type parameter. But there are those whom would like to see it changed to in instance parameter, for reasons of 'Flexibility'. There are Pro's & Con's for each. I was hoping to get a read from you nice folks on AUGI for your thoughts. Mine are listed below.
Thank you in advance,
Jeff S.
Pro's for Instance
Less family types
Less clicks to change angle
Less training
Con's for Instance
'Select All Instance' is based on type, and if the values are different, the parameter be empty
Harder to track down incorrect setting.
Adds more data to the project file than Type parameters, all be it minimally
Could lead to lazy modeling (if door swings collide, adjusting swing angle will hide issues)
Untested assumption: If parameter is modified, additional placements may take on incorrect values
Pro's for Type
Easier to identify and fix multiple instances of the doors
Naming convention would contain non-standard angles (not 90)
Harder for end users to change
Should be a limited number of angles (45, 90, 170), 90 being the baseline standard.
Con's of Type
Longer Type Names
More training maybe required
Limits 'Flexibility'