Quote -

Quote -
Viewing the value of a control as a displayed value between 0 and 1 (with however many decimals) or 0 and 100 (as a percentage) isn’t really helpful when the real meaning is for instance a door where the value in degrees varies between 0 (completely closed) and 90 (fully open). Many other examples could be provided with varying values and meanings. In general it would be better to display the value in a meaningful way, as varying with a specific resolution between a minimum and a maximum value and possibly with specific texts if only specific discreet values are valid. This of course only provides a means of displaying a very specific value and does not provide any indication of the relationship between the actual value and the valid range of values (which would probably best be indicated with some form of slider).

Well, allowing a control to display either a percentage or an angle measurement I think would be easy enough, the difficulty would be in trying to do additional scales like feet, inches, meters, etc.  

Not a real problem. Meters, feet, inches etcetera just need a standard multiplication/division factor, and you'd need an application-wide flag to indicate what unit the user wants, like Poser does in its .INI file. On-the-fly calculation of the value to display from this standard factor and the internal native unit is lightweight, easy and fast.
By the way, fast switching between preferred units and Poser native units (or maybe also FAST native units) would be very helpful for developers - when making ERC code you need to use native units.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff