Driving dimension should use default_dec_places value when formula is used for its calculation
- 4 replies
- 59 views
1. Describe the Problem
Default_dec_places is not working as expected in a specific case - see video attached.
Default_dec_places works correctly, when dimension is defined by an equation in the feature creator.
When driving dimension is modified by the same equation - resulting value has more decimal places.
Result dimension should have the same number of decimal places as specified in default_dec_places, or user should be clearly informed (maybe with a pop-up message) that displayed and actual dimensions are different.
Summary:
- Feature definition : dimension specified as 360/7, dimension - 51.429. Displayed dimension rounded to 51.429. Geometry length – 51.429 – Correct
- Driving dimension modification: dimension specified as 360/7. Dimension - 51.42857142857. Displayed dimension rounded to 51.429, Geometry length - 51.42857142857 - Incorrect
2. Are you using a workaround?
No workaround available. default_dec_places value is not respected, when driving dimension is edited.
3. What is the use case for your organization?
Using formulas to change position/size of a already created feature.
4. What impact does this problem currently have on your organization?
Difference between displayed and actual dimension can cause issues and wasted time in downstream processes like simulation, manufacturing, etc.
