[Flightgear-devel] A380 tutorial issues

2010-04-03 Thread Pigeon


Hi,

Was trying the A380 tutorial, and I noticed a property mismatch in
the no-smoking switch check:

  error
messageFlick no-smoking switch once on the overhead/message
condition
  not-equals
property/controls/switches/no-smoking/property
value1/value
  /not-equals
/condition
  /error

However, the exit condition has:

  greater-than
property/controls/switches/smoking/property
value0/value
  /greater-than

Changing no-smoking to smoking fixes it.


Also, on the cockpit display, the DEPARTURE and ARRIVAL light
seem to be reversed?

And btw, I'm probably dumb but I can't find the HDG button? :(

Thanks.


Pigeon.

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] A380 tutorial issues

2010-04-03 Thread Scott Hamilton
On Sat, 2010-04-03 at 22:44 +1100, Pigeon wrote:
 
 Hi,
 
   Was trying the A380 tutorial, and I noticed a property mismatch in
 the no-smoking switch check:
 
   error
 messageFlick no-smoking switch once on the overhead/message
 condition
   not-equals
 property/controls/switches/no-smoking/property
 value1/value
   /not-equals
 /condition
   /error
 
   However, the exit condition has:
 
   greater-than
 property/controls/switches/smoking/property
 value0/value
   /greater-than
 
   Changing no-smoking to smoking fixes it.


  Ah, good catch; there must be another logic error in there somewhere,
  because I have actually got through that section successfully. I'll
  have another look later.


 
 
   Also, on the cockpit display, the DEPARTURE and ARRIVAL light
 seem to be reversed?


   OK, I'm not sure where you mean here? do you mean the FMS input
   fields on the MCDU screen? Or do you mean once you get into the
   Active init flight plan, where you select the runways and SID/STAR,
   and the Departure and Arrival tabs (illuminated active tab) towards
   the top of the page?


 
   And btw, I'm probably dumb but I can't find the HDG button? :(

   That is the on the AFS control panel on the glareshield, the first
   knob left of the centre AP and FD buttons, click to push, 
   middle click to pull (managed and selected modes respectively)

   Feel free to e.mail me off-list if you have some more questions.



   Cheers
 S.


 
   Thanks.
 
 
 Pigeon.
 
 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel



--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] A380 tutorial issues

2010-04-03 Thread willie
Scott Hamilton wrote:
 On Sat, 2010-04-03 at 22:44 +1100, Pigeon wrote:
 Hi,

  Was trying the A380 tutorial, and I noticed a property mismatch in
 the no-smoking switch check:

   error
 messageFlick no-smoking switch once on the overhead/message
 condition
   not-equals
 property/controls/switches/no-smoking/property
 value1/value
   /not-equals
 /condition
   /error

  However, the exit condition has:

   greater-than
 property/controls/switches/smoking/property
 value0/value
   /greater-than

  Changing no-smoking to smoking fixes it.
 
 
   Ah, good catch; there must be another logic error in there somewhere,
   because I have actually got through that section successfully. I'll
   have another look later.
 
 

  Also, on the cockpit display, the DEPARTURE and ARRIVAL light
 seem to be reversed?
 
 
OK, I'm not sure where you mean here? do you mean the FMS input
fields on the MCDU screen? Or do you mean once you get into the
Active init flight plan, where you select the runways and SID/STAR,
and the Departure and Arrival tabs (illuminated active tab) towards
the top of the page?
 
 
  And btw, I'm probably dumb but I can't find the HDG button? :(
 
That is the on the AFS control panel on the glareshield, the first
knob left of the centre AP and FD buttons, click to push, 
middle click to pull (managed and selected modes respectively)
 
Feel free to e.mail me off-list if you have some more questions.
 
Please keep it on-list as this cleared up a couple of things for me too
- I just never got around to writing to the list.


Best Regards
Willie Fleming


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] A380 tutorial issues

2010-04-03 Thread Pigeon

OK, I'm not sure where you mean here? do you mean the FMS input
fields on the MCDU screen? Or do you mean once you get into the
Active init flight plan, where you select the runways and SID/STAR,
and the Departure and Arrival tabs (illuminated active tab) towards
the top of the page?


Sorry I wasn't very clear (and I wouldn't know how to describe it :)


Like in the tutorial, departing YSSY, arriving YMML:
http://pigeond.net/~pigeon/flightgear/a380-001.png


When I click on the DEPARTURE button, the screen shows:
http://pigeond.net/~pigeon/flightgear/a380-002.png

The heading shows ARRIVIAL. I suppose now I get it as I'm being at
the DEPARTURE screen, and the ARRIVIAL is for me to goto the ARRIVIAL
screen. Am I right?


And same for the ARRIVAL screen:
http://pigeond.net/~pigeon/flightgear/a380-003.png

Is it supposed to be like that?


Thanks again.


Pigeon.

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] A380 tutorial issues

2010-04-03 Thread Scott Hamilton
On Sun, 2010-04-04 at 09:03 +1000, Pigeon wrote:

 OK, I'm not sure where you mean here? do you mean the FMS input
 fields on the MCDU screen? Or do you mean once you get into the
 Active init flight plan, where you select the runways and SID/STAR,
 and the Departure and Arrival tabs (illuminated active tab) towards
 the top of the page?
 
 
   Sorry I wasn't very clear (and I wouldn't know how to describe it :)
 
 
   Like in the tutorial, departing YSSY, arriving YMML:
   http://pigeond.net/~pigeon/flightgear/a380-001.png
 
 
   When I click on the DEPARTURE button, the screen shows:
   http://pigeond.net/~pigeon/flightgear/a380-002.png
 
   The heading shows ARRIVIAL. I suppose now I get it as I'm being at
 the DEPARTURE screen, and the ARRIVIAL is for me to goto the ARRIVIAL
 screen. Am I right?



   Yes that is correct, the description below describes why and how it
can be fixed. But in summary, it was a 
   little more complicated to leave the active tab text there as you
move from tab to tab and page to page,
   so I just showed the available tabs and not the active tab.



 
 
   And same for the ARRIVAL screen:
   http://pigeond.net/~pigeon/flightgear/a380-003.png
 
   Is it supposed to be like that?


 OK, in real-life there are supposed to be two tabs; DEPARTURE and
ARRIVAL,  when a tab is active
 it has white text on a black background with a white outline, the
other available tabs
 have white text on a grey background with a white outline.

 So this isn't as complete as we would like, the grey background is
an object in the .ac file, the tab labels are
 text animations (and so are separate objects). We use a select
animation to turn on and off 
 the input fields, the input labels and the tab background + label
depending on what page and tab is active.

 To be able to click on a tab to make that active, it needs to
displayed; so thinking out loud, the active tab text label
 should be moved into a new select animation that is based just on
the page and not the page + tab this would
 then leave the white text label there for the active tab and it
will just have a black background from the layer below.



S.
 



 
 
   Thanks again.
 
 
 Pigeon.
 
 --
 Download Intel#174; Parallel Studio Eval
 Try the new software tools for yourself. Speed compiling, find bugs
 proactively, and fine-tune applications for parallel performance.
 See why Intel Parallel Studio got high marks during beta.
 http://p.sf.net/sfu/intel-sw-dev
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel