* Jon S Berndt -- Thursday 20 June 2002 18:14:
Any chance someone could post some screen shots of the
panel?
http://www.unet.univie.ac.at/~a8603365/fgfs4.jpeg
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
There are two aspects to being on the glide slope. First, are you on _any_ path
that ends up at the beginning of the runway? Second, are you on the _intended_ glide
slope?
For the first, I was taught to look at the intended landing spot and, being aware of
the windscreen, see whether that
Tony Peden wrote:
I think you mentioned that it was /accelerations/pilot-g's ?
I'd like to see some direction info added to the name as lateral accel
at the pilot seat is quite often of interest as well as normal.
So maybe:
/accelerations/pilot-normal-g and
/accelerations/pilot-lateral-g
Norman Vine wrote:
Check your editor's help file for 'multi-file grep' or 'multi-file search'
IMHO this is an indispensible editor feature for developing 'large'
projects and most 'good' code editors have this feature builtin so
you don't have to resort to using commandline tools directly.
Alex Perry writes:
C172 glide angle is about 1.4 miles per 1000 ft, which implies the
canadian pattern gives you 300 ft to land with. However, that
doesn't allow for the plane to make the initial 90 degree turn
towards the airport and for the plane to align itself with the
runway.
[EMAIL PROTECTED] writes:
For the second aspect, as David (I think) said, I was taught to
recognise the on-screen geometry of the runway, mainly the angle
of its edges. That works well in getting used to your home
airfield, and after gaining experience there, you will be
comfortable
Andy Ross writes:
Blam. Culture crash. Most of us unix geeks would contend until the
day we die that doing a recursive search via a GUI interface is slower
and more error prone than running find and grep.
Nah. I like running find, grep, and etags from inside Emacs, then
stepping
I agree that closer is better, but you have left something out of the
equation: if the engine failure is sudden (what we're assuming here, I
think), *and* you react quickly, you have an extra 25-45kt of airspeed
that you can trade for altitude before you get down to Vglide at 65
KIAS. That
Woohoo ... flame war!
* Andy Ross -- Thursday 20 June 2002 19:27:
I do this particular operation so much that I have a little 2-liner
cgrep script that looks for a string in all the C/C++ source files
under a directory.
Hey, cgrep is already defined like this:
#!/bin/bash
trap echo -en
Andy Ross writes:
Norman Vine wrote:
Check your editor's help file for 'multi-file grep' or
'multi-file search'
IMHO this is an indispensible editor feature for developing 'large'
projects and most 'good' code editors have this feature builtin so
you don't have to resort to using
David Megginson writes:
Andy Ross writes:
Blam. Culture crash. Most of us unix geeks would contend until the
day we die that doing a recursive search via a GUI
interface is slower
and more error prone than running find and grep.
Nah. I like running find, grep, and etags from inside
On Thu, 20 Jun 2002 19:46:30 +0200
Melchior FRANZ [EMAIL PROTECTED] wrote:
Woohoo ... flame war!
Grep, schmep. It can't come close to actually printing out
a copy of the source code and looking through it manually.
I mean, if you want accuracy, what can beat a pair of
human eyes and some
I really have to learn to type eventually 8-(
---
Norman, I'm glad that you brought that up (it was my next question):
What code editors do people recommend using? I can sort-of use vi, the
one time I started emacs, I couldn't exit the darn thing.
I'm evaluating a lite
* ima sudonim -- Thursday 20 June 2002 20:19:
the one time I started emacs, I couldn't exit the darn thing.
$ killall -9 emacs; alias emacs=vim
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
* Jon S Berndt -- Thursday 20 June 2002 18:14:
Any chance someone could post some screen shots of the
panel?
http://www.unet.univie.ac.at/~a8603365/fgfs4.jpeg
I get that, too. What I'm missing in recent releases is display of the gear
in the outside view and keyboard control of throttle
Martin Spott wrote:
I get that, too. What I'm missing in recent releases is display of the
gear in the outside view and keyboard control of throttle and
flaps. This appeared to be introduced the the recent A-4 updates in
YASim. Can anyone confirm ?
Works for me. Are you sure you have a
Martin Spott wrote:
I get that, too. What I'm missing in recent releases is display of the
gear in the outside view and keyboard control of throttle and
flaps. This appeared to be introduced the the recent A-4 updates in
YASim. Can anyone confirm ?
Works for me. Are you sure you have a
Martin Spott [EMAIL PROTECTED] said:
I get that, too. What I'm missing in recent releases is display of the gear
in the outside view and keyboard control of throttle and flaps. This
appeared to be introduced the the recent A-4 updates in YASim.
Can anyone confirm ?
Martin,
This sounds
[EMAIL PROTECTED] wrote:
There are two aspects to being on the glide slope. First, are you on _any_ path
that ends up at the beginning of the runway? Second, are you on the _intended_ glide
slope?
For the first, I was taught to look at the intended landing spot and, being aware of
the
* [EMAIL PROTECTED] (ima sudonim) [2002.06.20 13:20]:
Norman, I'm glad that you brought that up (it was my next question):
What code editors do people recommend using? I can sort-of use vi, the
one time I started emacs, I couldn't exit the darn thing.
My experience with emacs started out
On Thursday, 20, 2002, at 09:55AM, Norman Vine [EMAIL PROTECTED] wrote:
FYI
http://www.businessweek.com/technology/content/jun2002/tc20020618_2463.htm?r
ef=cnet
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
On Thursday, June 20, 2002, at 01:19 PM, ima sudonim wrote:
I'd like to have something that I could set up to do my compiles, go from
errors straight to an editing session at the point of error. Find in
file like grep or the ability to call an external command like grep would
be great
On Thu, 2002-06-20 at 09:06, Norman Vine wrote:
ima sudonim writes:
Incidentally, how does one find within files using grep? If
i'm in /src
and want to search all components of /src (including recursively
directories)
I tried:
find . | grep -i joy but that finds just files with
On Thu, 2002-06-20 at 09:04, [EMAIL PROTECTED] wrote:
from:Tony Peden [EMAIL PROTECTED]
I'd like to see some direction info added to the name as lateral accel
at the pilot seat is quite often of interest as well as normal.
So maybe:
/accelerations/pilot-normal-g and
On Thu, 2002-06-20 at 10:14, Andy Ross wrote:
Tony Peden wrote:
I think you mentioned that it was /accelerations/pilot-g's ?
I'd like to see some direction info added to the name as lateral accel
at the pilot seat is quite often of interest as well as normal.
So maybe:
Alex Perry writes:
My docs recommend doing 80 kias on downwind, giving you only 15 knots
of margin to trade into height. Tests have shown that pilots spend
about six seconds sitting in stunned amazement, after engine failure,
before doing through their ABCs when it happens for-real and
Christian Mayer writes:
For the first, I was taught to look at the intended landing spot
and, being aware of the windscreen, see whether that spot is
stationary relative to the windscreen. If so, you are on track
toward that spot. Try to see and feel this before worrying about
I just updated to the latest CVS for SimGear and tried to build. While Mac OS X builds like a champ, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another
I haven't tried building this, but this sort of error looks like you just
have to put a
using namespace std;
into the props.cxx
Cheers, Christian
At 07:50 PM 20/06/2002 -0500, you wrote:
I just updated to the latest CVS for SimGear and tried to build. While Mac
OS X builds like a champ,
Grep, schmep. It can't come close to actually printing out
a copy of the source code and looking through it manually.
I mean, if you want accuracy, what can beat a pair of
human eyes and some bright white inkjet paper? I've even
got grep aliased to print all .cpp files in draft mode
I didn't see anything like that in the new files, but I may not know what,
exactly, I should be looking for. The only new using clause was in
props.cxx:
using std::find;
Jonathan Polley
On Thursday, June 20, 2002, at 08:02 PM, Christian Stock wrote:
I haven't tried building this, but
David Megginson wrote:
Andy Ross writes:
This panel isn't quite right, though. The center attitude indicator
isn't a flat card, but is in fact a rotating globe.
This might be a good time to mention that we have an alternative
method for creating panels. 3D models can now include other
I have submitted a patch to David. Here is what is needed :
SG_USING_STD(find);
SG_USING_STD(vectorSGPropertyChangeListener *);
SG_USING_STD(vectorSGPropertyNode *);
around line 29 of props.cxx
-Fred
- Original Message -
From: Jonathan Polley [EMAIL PROTECTED]
I didn't see anything
33 matches
Mail list logo