Re: [Flightgear-devel] map question
Hi Syd, On 31 Dec 2010, at 08:55, syd adams wrote: I see a large portion of mine could be affected I can change all those to fit the new layout. So how do I go about committing updates ? Who do i contact about write access , or is a merge request the way to go? Or possibly create a gitorious repository for each of mine ? Would guess that making one personal clone would be sufficient. You can push changes for all your aircraft to that repository and create a merge request once you believe your changes are ready to be merged into fg/gitorious. I personally, prefer merge requests, because it's a very convenient way to check what changes are still required to handle. I have read some reports that creating the merge requests is a bit tricky at the moment do to gitorious capacity limits, but I cannot comment on that right now. And Happy New Year , everyone! Thanks! I wish to second that. Cheers, Durk -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] map question
Here's a dumb question: I see the built in flightgear map dialog is activated in the 777-200ER, but disabled (grayed out) for the F-14b. I can't find the mechanism or place where this is set. How can i control the availability of the map dialog? Thanks, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
On 30 Dec 2010, at 16:01, Curtis Olson wrote: I see the built in flightgear map dialog is activated in the 777-200ER, but disabled (grayed out) for the F-14b. I can't find the mechanism or place where this is set. How can i control the availability of the map dialog? That's weird - I wrote the dialog, and originally added it to the 'Autopilot' menu - next to the route manager. When the menubar was recently cleaned up, it was moved tot he 'Equipment' menu - which I wholeheartedly agree with, since the Autopilot menu is disabled on the C172, for example. As far as I know, the menu item is 'just' a regular entry in the Equipment menu, so I would guess the f14 would be disabling it - but that seems quite unlikely too. We should probably find out if it's deliberate or accidental. James -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
On Thu, Dec 30, 2010 at 11:18 AM, James Turner wrote: On 30 Dec 2010, at 16:01, Curtis Olson wrote: I see the built in flightgear map dialog is activated in the 777-200ER, but disabled (grayed out) for the F-14b. I can't find the mechanism or place where this is set. How can i control the availability of the map dialog? That's weird - I wrote the dialog, and originally added it to the 'Autopilot' menu - next to the route manager. When the menubar was recently cleaned up, it was moved tot he 'Equipment' menu - which I wholeheartedly agree with, since the Autopilot menu is disabled on the C172, for example. As far as I know, the menu item is 'just' a regular entry in the Equipment menu, so I would guess the f14 would be disabling it - but that seems quite unlikely too. We should probably find out if it's deliberate or accidental. I've been grepping for Map, map, dialog and haven't turned up anything yet that seems to connect. Any suggestions what keywords I should even be grepping for? I haven't been able to find any promising references in the f-14b tree. Thanks, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
The F14 disables the first menu item from the 5th menu ext_stores.nas = setprop(sim/menubar/default/menu[5]/item[0]/enabled, 0); Not sure which menu item originally was at this location. Quite bad. Harded coded hacks like this just always break... ;) cheers, Thorsten On Thu, Dec 30, 2010 at 6:26 PM, Curtis Olson curtol...@gmail.com wrote: On Thu, Dec 30, 2010 at 11:18 AM, James Turner wrote: On 30 Dec 2010, at 16:01, Curtis Olson wrote: I see the built in flightgear map dialog is activated in the 777-200ER, but disabled (grayed out) for the F-14b. I can't find the mechanism or place where this is set. How can i control the availability of the map dialog? That's weird - I wrote the dialog, and originally added it to the 'Autopilot' menu - next to the route manager. When the menubar was recently cleaned up, it was moved tot he 'Equipment' menu - which I wholeheartedly agree with, since the Autopilot menu is disabled on the C172, for example. As far as I know, the menu item is 'just' a regular entry in the Equipment menu, so I would guess the f14 would be disabling it - but that seems quite unlikely too. We should probably find out if it's deliberate or accidental. I've been grepping for Map, map, dialog and haven't turned up anything yet that seems to connect. Any suggestions what keywords I should even be grepping for? I haven't been able to find any promising references in the f-14b tree. Thanks, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/ -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
Oh, this actually shows a larger problem. Obviously it isn't too uncommon for aircraft to disable or override specific menu items - mainly affects menu items for the radio stack and autopilot. Unfortunately all of this is done using fixed menu item positions - e.g. 5th menu, 3rd item... So any change of the menu item ordering currently breaks lots of planes. And obviously the recent menubar overhaul has done just that. We'll need to adapt all the aircraft using such hacks to the changed menu structure. And might need to think about a better solution to avoid future problems of this kind. I did a quick grep to find potentially affected aircraft (couldn't verify if their menus are all broken now, but that's the ones overriding or disabling specific menu items using fixed positions): 717 737-300 737NG600 737NG700 737NG800 737NG900 747-400 757-200 777-200 A320-family A380 Aerostar-700 b1900d Citation-Bravo CitationX CRJ-200 CRJ-900 f16 f-14b fokker100 MiG-15 VMX22-Osprey = All the aircraft above override the radio and/or autopilot dialogs. Except for the MiG15, which just disables one dialog (like the f14). So, what do we do? Adapt all the aircraft above - or revert the menu item ordering? cheers, Thorsten On Thu, Dec 30, 2010 at 6:37 PM, ThorstenB bre...@gmail.com wrote: The F14 disables the first menu item from the 5th menu ext_stores.nas = setprop(sim/menubar/default/menu[5]/item[0]/enabled, 0); Not sure which menu item originally was at this location. Quite bad. Harded coded hacks like this just always break... ;) cheers, Thorsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
The f-14b used to disable the fuel menu item, because it uses a special one. It used to be the first menu item on the Equipment menu, maybe that's why the map got disabled instead. Oh, this actually shows a larger problem. Obviously it isn't too uncommon for aircraft to disable or override specific menu items - mainly affects menu items for the radio stack and autopilot. Unfortunately all of this is done using fixed menu item positions - e.g. 5th menu, 3rd item... So any change of the menu item ordering currently breaks lots of planes. And obviously the recent menubar overhaul has done just that. We'll need to adapt all the aircraft using such hacks to the changed menu structure. And might need to think about a better solution to avoid future problems of this kind. I did a quick grep to find potentially affected aircraft (couldn't verify if their menus are all broken now, but that's the ones overriding or disabling specific menu items using fixed positions): 717 737-300 737NG600 737NG700 737NG800 737NG900 747-400 757-200 777-200 A320-family A380 Aerostar-700 b1900d Citation-Bravo CitationX CRJ-200 CRJ-900 f16 f-14b fokker100 MiG-15 VMX22-Osprey = All the aircraft above override the radio and/or autopilot dialogs. Except for the MiG15, which just disables one dialog (like the f14). So, what do we do? Adapt all the aircraft above - or revert the menu item ordering? cheers, Thorsten On Thu, Dec 30, 2010 at 6:37 PM, ThorstenB bre...@gmail.com wrote: The F14 disables the first menu item from the 5th menu ext_stores.nas = setprop(sim/menubar/default/menu[5]/item[0]/enabled, 0); Not sure which menu item originally was at this location. Quite bad. Harded coded hacks like this just always break... ;) cheers, Thorsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
On 30 Dec 2010, at 18:18, ThorstenB wrote: So, what do we do? Adapt all the aircraft above - or revert the menu item ordering? Adapt the ordering in the short term, and then come up with a non-brittle solution for the future. The new menu arrangement is significantly better than the old one. James -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
James Turner a écrit : On 30 Dec 2010, at 18:18, ThorstenB wrote: So, what do we do? Adapt all the aircraft above - or revert the menu item ordering? Adapt the ordering in the short term, and then come up with a non-brittle solution for the future. The new menu arrangement is significantly better than the old one. James Thanks all for pointing the problem. Yes, it was intended to disable the stock Fuel and Payload menu. I'll adapt the code to follow the new ordering. It should be in git very soon. Alexis -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
Actually this might not be so bad, as I think your grep may have returned some false positives. The A380, 747-400 and 737NG800 only add an aircraft specific menu and add Pushback to the Equipment menu, they don't disable any existing menu items. However giving menu items an alias name or unique id is still worth doing, and a way to check if an alias is present before adding new items would be nice as well. S. On Thu, 2010-12-30 at 19:18 +0100, ThorstenB wrote: Oh, this actually shows a larger problem. Obviously it isn't too uncommon for aircraft to disable or override specific menu items - mainly affects menu items for the radio stack and autopilot. Unfortunately all of this is done using fixed menu item positions - e.g. 5th menu, 3rd item... So any change of the menu item ordering currently breaks lots of planes. And obviously the recent menubar overhaul has done just that. We'll need to adapt all the aircraft using such hacks to the changed menu structure. And might need to think about a better solution to avoid future problems of this kind. I did a quick grep to find potentially affected aircraft (couldn't verify if their menus are all broken now, but that's the ones overriding or disabling specific menu items using fixed positions): 717 737-300 737NG600 737NG700 737NG800 737NG900 747-400 757-200 777-200 A320-family A380 Aerostar-700 b1900d Citation-Bravo CitationX CRJ-200 CRJ-900 f16 f-14b fokker100 MiG-15 VMX22-Osprey = All the aircraft above override the radio and/or autopilot dialogs. Except for the MiG15, which just disables one dialog (like the f14). So, what do we do? Adapt all the aircraft above - or revert the menu item ordering? cheers, Thorsten On Thu, Dec 30, 2010 at 6:37 PM, ThorstenB bre...@gmail.com wrote: The F14 disables the first menu item from the 5th menu ext_stores.nas = setprop(sim/menubar/default/menu[5]/item[0]/enabled, 0); Not sure which menu item originally was at this location. Quite bad. Harded coded hacks like this just always break... ;) cheers, Thorsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
On Thu, Dec 30, 2010 at 10:47 PM, Citronnier - Alexis Bory wrote: Yes, it was intended to disable the stock Fuel and Payload menu. I'll adapt the code to follow the new ordering. It should be in git very soon. On Thu, Dec 30, 2010 at 10:52 PM, Scott Hamilton wrote: Actually this might not be so bad, as I think your grep may have returned some false positives. The A380, 747-400 and 737NG800 only add an aircraft specific menu and add Pushback to the Equipment menu, they don't disable any existing menu items. However giving menu items an alias name or unique id is still worth doing, and a way to check if an alias is present before adding new items would be nice as well. Please wait before committing any related changes! There is also a bug report to track this problem: http://code.google.com/p/flightgear-bugs/issues/detail?id=231 I still vote for keeping the original menu ordering in the Equipment menu for the upcomming release, otherwise we have another incompatibility - and a very unnecessary one. It's very simple to avoid this issue for this release (keep fuelpayload/radio/autopilot menu items in original position). And it may still affect more planes (those not in GIT). Also, currently we have no clean solution for this issue. So any change now would require adapting the aircraft now, and then again for the next release. I think it's better to keep the original ordering for now, then provide a proper solution (i.e. option to override/disable menu items via symbolic names) for the next release. Aircraft then only need to be changed once. cheers, Thorsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] map question
I see a large portion of mine could be affected I can change all those to fit the new layout. So how do I go about committing updates ? Who do i contact about write access , or is a merge request the way to go? Or possibly create a gitorious repository for each of mine ? I,ve got FG installed on a new laptop , (old computer finally retired) , so I'm back to fixing my aircraft , just not sure what to do with them now. While I'm on the subject of aircraft updates , I'm about to map 2 keys for the Aerostar's rocker switch steering . It would be nice to keep to some standard, so has anyone else done this and if so , which 2 keys were used ? If not , any suggestions on a set of keys ? Thanks, Syd And Happy New Year , everyone! -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
