* Tim Moore -- Wednesday 08 April 2009: > I'm trying to give your generic approach a chance. I think a system > where you have to explicitly trigger a listener is a poor substitute > for one where the listener is fired automatically.
But you'd only have to do it manually from the property browser or from telnet. In almost all cases it would be done from C++ or Nasal via wrapper functions, so not exactly manual either. > And I do think > <diffuse-atomic> > <red>.2</red><green>.3</green><blue>.4</blue> > </diffuse-atomic> > blows compared to > <diffuse>.2 .3 .4</diffuse> > but perhaps that's just me. But that's again the XML representation argument. As I said before, while I'm not thrilled about it, it's not what worries me. You could have a custom XML reader read that into three separate properties without problems. Just look at YASim's XML reader or the AI code's. What I find bad is the aggregate property type. > Better not tell anyone about our secret correspondence on the issue. > Oh. Whoops. > Seriously, suggesting that individual conversation among colleagues and > friends is "secret" and suspect [...] It's just that Curt referred to what you told him in private conversation apparently as a base for his opinion about the matter. And I think that others could use that same information as well to form theirs. Unless there's stuff that only Curt should know about it, of course. ;-) m. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
