[Flightgear-devel] property sytem - design guidelines
Hi, just a quick question: are there any guidelines regarding the scope at which property system values should be accessed? E.g., when should classes communicate values via the property system (if at all)? At which level in the program structure / by which entities should the property system be used? thanks, Manuel ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] property sytem - design guidelines
Manuel Massing wrote: Hi, just a quick question: are there any guidelines regarding the scope at which property system values should be accessed? E.g., when should classes communicate values via the property system (if at all)? At which level in the program structure / by which entities should the property system be used? As much as possible. It allows external scripts/animations to use the internals if necessary. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] property sytem - design guidelines
just a quick question: are there any guidelines regarding the scope at which property system values should be accessed? E.g., when should classes communicate values via the property system (if at all)? At which level in the program structure / by which entities should the property system be used? My thinking is that parameters should only be published and made visible when they are needed (or might be needed) by external scripts or specifications. Then, make sure that they are only writable when necessary. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
