Re: [Flightgear-devel] RFC: Committing conditional compile patch for ATCDCL
Hi Curt, On Wednesday 23 December 2009 03:35:31 pm Curtis Olson wrote: On Wed, Dec 23, 2009 at 1:53 AM, Durk Talsma d.tal...@xs4all.nl wrote: Probably the biggest thing to worry about is if you introduce a new #define is the folks doing windows builds. Configure takes care of keeping everything consistent for unix builds, but depending on how this is done it could cause weird breakage for windows builds if the developers aren't aware they need to add a new define to their build environment. Thanks for the comment. Since I'm using the same mechanism that we are using for other conditional compiles, I don't really expect any major issues here. Since I have not seen any major objections, I will go ahead and try to commit this code later today. Cheers, Durk -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: Committing conditional compile patch for ATCDCL
On Wednesday 30 December 2009 10:21:20 am Durk Talsma wrote: Thanks for the comment. Since I'm using the same mechanism that we are using for other conditional compiles, I don't really expect any major issues here. Since I have not seen any major objections, I will go ahead and try to commit this code later today. Okay, done. For linux / autoconf builds nothing should have changed for the default situation (this actually took a little more testing to confirm on my side). For windows builders, you might find that your need to define ENABLE_ATCDCL to a non zero value somewhere and then everything should work as advertized again. Cheers, Durk -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] adding CenturyIIB and CenturyIII to AP list in gui.nas
Hi, Does anyone object to graying out the autopilot menu for tw additional autopilots used by several aircraft? If not, would someone with commit authority please apply the following simple patch? Index: gui.nas === RCS file: /var/cvs/FlightGear-0.9/data/Nasal/gui.nas,v retrieving revision 1.121 diff -u -p -r1.121 gui.nas --- gui.nas16 Nov 2009 20:40:15 -1.121 +++ gui.nas29 Dec 2009 17:43:02 - @@ -103,7 +103,10 @@ _setlistener(/sim/signals/nasal-dir-ini # enable/disable menu entries menuEnable(fuel-and-payload, fdm == yasim or fdm == jsb); -menuEnable(autopilot, props.globals.getNode(/autopilot/KAP140/locks) == nil); +menuEnable(autopilot, props.globals.getNode(/autopilot/KAP140/locks) == nil + and props.globals.getNode(/autopilot/CENTURYIIB/locks) == nil + and props.globals.getNode(/autopilot/CENTURYIII/locks) == nil +); menuEnable(multiplayer, multiplayer.is_active()); menuEnable(tutorial-start, size(props.globals.getNode(/sim/tutorials, 1).getChildren(tutorial))); menuEnable(joystick-info, size(props.globals.getNode(/input/joysticks).getChildren(js))); Thanks, Dave P. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] adding CenturyIIB and CenturyIII to AP list in gui.nas
On Wed, Dec 30, 2009 at 2:21 PM, dave perry skida...@mindspring.com wrote: Hi, Does anyone object to graying out the autopilot menu for tw additional autopilots used by several aircraft? I would suggest introducing an enable switch for the generic autopilot, the state of which would be reflected in the menu status as well. Specific autopilots could then disable the generic one. Ideally, the generic autopilot shouldn't even get loaded - I'd exile it from preferences.xml to the aircraft files. If an aircraft doesn't have a custom autopilot it should load the generic one explicitly. I'd even consider simply moving the menu disable call itself into the specific autopilot nasal files a better solution than listing special cases in gui.nas. -- Csaba/Jester -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Update FG Short Reference
YOSHIMATSU Toshihide wrote: Hi Stuart and Martin, I'm translating the FlightGear Manual into Japanese in FlightGear JP forum. After v1.9.0 released, I have noticed some typos and/or points to reconsider the Manual. There is some notes about it (sorry, including Japanese language): http://flightgear.jpn.org/wiki/index.php?%A5%DE%A5%CB%A5%E5%A5%A2%A5%EB%A4%CE%CD%D7%BD%A4%C0%B5%C5%C0 If you can reflect some of these points in next Manual, I'm happy. Cheers, Toshi Thanks very much for the feedback. I'll be applying it to The Manual shortly. Regards, -Stuart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
