Re: [Flightgear-devel] Re: AP messed up? agl-hold vs. terrain-follow

2006-04-08 Thread Lee Elliott
On Friday 07 April 2006 07:56, Melchior FRANZ wrote:
 * Lee Elliott -- Friday 07 April 2006 00:31:
  now all we need from everyone else is a decision on
  'agl-hold' vs. 'terrain-follow'.

 Okay. I flipped a coin, and agl-hold won!  :-P

 No, seriously: If nobody objects I will tomorrow switch all
 remaining occurrences of terrain-follow to agl-hold in generic
 FlightGear files (but not in maintained aircraft, unless the
 maintainer wishes so). Rationale:

  - $FG_ROOT/Aircraft/Generic/generic-autopilot.xml uses
 agl-hold - $FG_ROOT/gui/dialogs/autopilot.xml uses agl-hold
 (and did before my changes) - all /autopilot/locks/altitude
 options end with -hold. (all heading options, too, except
 wing-leveler, which is understandable)

 Only $FG_ROOT/keyboard.xml and these aircraft use
 terrain-follow in at least one *.nas or *.xml file:

  - AN-225
  - BAC-TSR2
  - A-10
  - B-52F
  - YF-23
  - seahawk
  - MiG-15
  - TU-114
  - Hunter
  - CanberraBI8

 m.

Apart from the Hunter, which Vivian did, and the seahawk, which 
Vivian has done a lot of work on, the others were all done by 
me.  A simple search  replace on 'terrain-follow' /should/ work 
but will result in some funny property node names.

I'll go through them manually and get updates out.

Vivian: do you want to do the seahawk or shall I?  I guess we 
need to rationalise the seahawk anyway.

LeeE



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Re: AP messed up? agl-hold vs. terrain-follow

2006-04-07 Thread Melchior FRANZ
* Lee Elliott -- Friday 07 April 2006 00:31:
 now all we need from everyone else is a decision on 'agl-hold' vs.
 'terrain-follow'. 

Okay. I flipped a coin, and agl-hold won!  :-P

No, seriously: If nobody objects I will tomorrow switch all remaining 
occurrences
of terrain-follow to agl-hold in generic FlightGear files (but not in maintained
aircraft, unless the maintainer wishes so). Rationale:

 - $FG_ROOT/Aircraft/Generic/generic-autopilot.xml uses agl-hold
 - $FG_ROOT/gui/dialogs/autopilot.xml uses agl-hold (and did before my changes)
 - all /autopilot/locks/altitude options end with -hold.
   (all heading options, too, except wing-leveler, which is understandable)

Only $FG_ROOT/keyboard.xml and these aircraft use terrain-follow in at least
one *.nas or *.xml file:

 - AN-225
 - BAC-TSR2
 - A-10
 - B-52F
 - YF-23
 - seahawk
 - MiG-15
 - TU-114
 - Hunter
 - CanberraBI8

m.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Re: AP messed up? agl-hold vs. terrain-follow

2006-04-06 Thread Lee Elliott
On Thursday 06 April 2006 10:50, Melchior FRANZ wrote:
 * Melchior FRANZ -- Wednesday 05 April 2006 07:51:
  * Lee Elliott -- Tuesday 04 April 2006 22:49:
   There also seem to be some quirks in the way that the A/P
   gui handles things - if you already have an A/P mode
   engaged but didn't set it via the gui it will not be shown
   as set in the gui and then when you close the gui that
   setting becomes un-set.
 
  That's already fixed in my version of the dialog.

 Which is now committed. I waited for cvs being tagged for
 release, because I wasn't sure if it would work well enough
 already. But it seems to work without problems, so, if a
 packager wants to include it despite it being in 'instable'
 CVS/HEAD only ... :-)

 I also (think I) fixed a bug in gui.nas, that sometimes
 prevented the autopilot menu entry from getting activated when
 it should.

 m.

Fixing the behaviour is good work, now all we need from everyone 
else is a decision on 'agl-hold' vs. 'terrain-follow'.

Either is ok to me but as I mentioned, agl-hold is quicker to 
type while you're testing stuff (although my fingers now 
'remember' 'terrain-follow' :)

LeeE



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Re: AP messed up? agl-hold vs. terrain-follow

2006-04-04 Thread Melchior FRANZ
* Lee Elliott -- Tuesday 04 April 2006 22:49:
 On Monday 03 April 2006 19:54, Melchior FRANZ wrote:
  There seems to be a problem with terrain following:
 
  - the keyboard binding (Ctrl-t) uses terrain-follow
  - the AP dialog uses agl-hold

 The original value was 'terrain-follow' and agl-hold turned up 
 later, along with the A/P gui iirc.

That's really something that should get fixed before the release.
A quick searchreplace job. One just needs to know which version
to standardize on:  terrain-hold or agl-hold ?


 
 There also seem to be some quirks in the way that the A/P gui 
 handles things - if you already have an A/P mode engaged but 
 didn't set it via the gui it will not be shown as set in the gui 
 and then when you close the gui that setting becomes un-set.

That's already fixed in my version of the dialog. I'll commit that
after the release. It removes file $FG_ROOT/Nasal/autopilot.nas
(containing dialog helper functions), and adds some new Nasal code
to the $FG_ROOT/gui/dialog/autopilot.xml dialog directly. The new
dialog always reflects the actual AP state. Values in the input
fields are updated as you click on the virtual AP on the panel or
press CurUp/Down etc. Checkboxes  radiobuttons go on and off as
you press Ctrl-a, Ctrl-h, etc.

m.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel