Erik Hofman wrote: > Frederic Bouvier wrote: > > > option has_param type property b_param s_param func > > where: > > option : name of the option > > has_param : option is --name=value if true or --name if false > > type : OPTION_BOOL - property is a boolean > > OPTION_STRING - property is a string > > OPTION_DOUBLE - property is a double > > OPTION_INT - property is an integer > > OPTION_CHANNEL - name of option is the name of a channel > > OPTION_FUNC - the option trigger a function > > b_param : if type==OPTION_BOOL, value set to the property (has_param is > > false for boolean) > > s_param : if type==OPTION_STRING, value set to the property if has_param is > > false > > func : function called if type==OPTION_FUNC. if has_param is true, the > > value is passed > > to the function as a string, otherwise, 0 is passed. > > > > For OPTION_DOUBLE and OPTION_INT, the parameter value is converted into a > > double or an integer and set to the property. > > For OPTION_CHANNEL, add_channel is called with the parameter value as the > > argument. > > BTW. This is a good step in the direction of XML defined options. > Except for options that need to call a function, all can be implemented > to add options to FlightGear without the need to program any code!
Yes, but usually, options refer to code. How useful is it to configure multiplayer options in XML when you have to add a whole bunch of files to have this functionality ? -Fred _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
