Anuncios
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!

Make data entry consistently retain the accuracy of its value in the Properties box for parameters of Type Length.

Data entry in the Properties box for a family parameter of type "Length" (Project Units Length set to Feet and fractional inches) will override the accuracy of decimal entries by converting it to a fractional representation (to the nearest 1/256).  A value entered as 0.20 inches in the Properties box gets converted to 51/256" (actual value 0.199219) instead of retaining the actual entered value of 0.20 inches.  Inconsistently data entered by clicking on the displayed value in a family retains the actual value of 0.20 inches even though the Properties box display still shows 51/256".  Oddly enough, once the value is set to 0.20 inches by clicking the family parameter, entering the same value in the Properties box does NOT override/change the value.  However, changing the value to 0.15 inches and then back to 0.20 inches in the Properties box results in the aberrant behavior of the actual value changing to 0.199219 inches.

 

Use the attached Revit family to verify this behavior.  The results are consistent in Revit 2018 through Revit 2021.

 

Data entry accuracy should be retained no matter where the data is entered or how it is formatted for display.

 

Also, I would greatly appreciate it if folks would refrain from posting about the merits of the metric system and/or how mathematical rounding works.  Neither is relevant here.

 

Before posting a response, download the family and try the two methods of entering a value of 0.20 inches for the "Width Per Occupant" parameter.  Also note that if the Project Units Length is changed from "Feet and fractional inches" to "Decimal inches" the data entry is consistent between both methods ("Decimal feet" does not work).  However, it is unreasonable to expect Project Units to be modified prior to specific data entry and then switched back to the desired unit type.  Additionally, the work-around is to simply use a parameter of type "Number" instead of type "Length" where decimal entry is desired.