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 g
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 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
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
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 arr
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 on
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 spec
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 chan
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
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 cont
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 w
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
12 matches
Mail list logo
