On 10/11/2007, dave perry <[EMAIL PROTECTED]> wrote: > I just looked at the changes in cvs. There is a significant problem > with at least this implementation of one "key" to turn on all the lights > for all AC. There is no standard followed for how to implement nasal > electrical systems. The patches you made to cvs will accomplish your > stated goal for the pa24 and pa28, but not for the SenecaII or the > dhc2. This is because when I wrote electrical.nas for the pa28, I > started from the eleictrical.nas for the pa24. Some of the nasal > electrical systems bypass switches all together and toggle properties > such as /electrical/landinglights. Others include functional circuit > breakers that would need to be verified.
This sounds like a pretty big problem beyond just my patch. Nasal has been great for letting people add functionality to FlightGear, but it causes a lot of problems for the property system, especially when people use different property names, override stuff, etc. It might be time for a refactoring pass through some of the models. > A second observation is that I virtually never turn on the white cabin > light or the map light because I don't want to ruin my night vision. So > even for the pa24, I would not want to have all the light on for most > flights. I know -- I don't turn them on either -- but I put them in just for completeness for now. I have no problem pulling them out, once we agree on a common subset (and fix some of the property inconsistencies). All the best, David ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
