US customary Units ...works perfectly for me. as does Imperial decimal...as does default metric
Now I am going to chuck a fit! WHAT EXACTLY
ARE YOU ALL TALKING ABOUT....I AM SO SICK AND TIRED OF IDIOTIC SO CALLED BUG REPORTS WHERE ALL THE INFORMATION IS NOT PROVIDED!!!!!! aaaaaahhhhhh!!!! Thanks for just wasting another half hour of my time.
Now that I have that out of my system,
will each of the three of you post back with an exact
step by step explanation of what you are talking about,
Provide a demo file
what Units system have you set ? does changing it make any difference?
bronson wrote:Just curious, why is this?
I'm sorry but I don't remember why. It wasn't always that way, at one time the leading zero wasn't required when entering the length of a numerical distance constraint for values less than 1.
Writing without the leading zero is wrong, it is not correct maths in English at least, (obviously other languages may be different) its just a silly lazy incorrect way to write, so honestly I was surprised to see that it does work. The only place for me that it does not see to work is default mm, if I add m, or ", or in, my values are accepted without the leading zero.
Once you guys actually give me the information to exactly duplicate what you are doing, I will test again ...but as far as I can see it is all working perfectly here...could be platform specific ....but I am not going to test any more until I have something exact and specific to test.
OS: Ubuntu 12.04.5 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.16.6451 (Git)
Build type: Release
Python version: 2.7.3
Qt version: 4.8.2
Coin version: 3.1.3
OCC version: 6.9.1.oce-0.18-dev