Tony Peden <[EMAIL PROTECTED]> said: > On Thu, Feb 28, 2002 at 10:25:36AM -0800, Andy Ross wrote: > > Tony Peden wrote: > > > David Megginson wrote: > > > > Tony Peden wrote: > > > > > I certainly like the idea of having some sort of units indicator > > > > > on every property name, though I agree risk of breakage is high > > > > > in this case. > > > > > > > > I can change everything in FlightGear and the base package, but I'm > > > > worried about breaking people's private config files, especially for > > > > joysticks. > > > > > > Well, leaving them as they are certainly won't be a problem for the > > > current developers -- the units for those have been percent for as long > > > as I can remember. And percent are non-dimensional, so no units > > > indicator is probably just as correct as -pct or -nd or whatever. > > > > I agree in general. I'd suggest the use of -fraction or somesuch > > instead of -pct if the range is 0:1, as it is for most of these > > properties currently. Even non-dimensional numbers need units to tell > > you how to interpret them. Sometimes percent really is more > > appropriate; consider N1 and N2 turbine speeds. > > OK, if you really want to save percent for 0-100 quantities, how about > something a little shorter than -fraction, -ratio > (-fraction is perfectly good, just long)
But if those settings don't represent a form of units--just arbitrary values, why do they need a suffix? The suffixes were intended to reflect units and make sense only when they mean something, like knowing if the value is in feet or meters, degrees or radians, knots or fps. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
