Justin Smithies wrote:
I seem to have the {} () ; wrong somewhere and maybe some other
little errors.
You didn't close the parentheses in the setlistener() call. Every (
must be matched with a ) of course. Programmers use indentation
conventions (and usually special editors) to help with
Dave Perry wrote:
I would like to add a voltage check before moving the flaps or
landing gear in data/Nasal/controls.nas. The proposed changes are
underlined.
Adding aircraft-specific code to the generic control mappings is a bad
idea; that file is for Nasal code that is globally useful for
Melchior FRANZ wrote:
If the object is removed from memory, then a variable is changed in
the object's namespace, so that the code can stop itself.
Rather than set this from C++ code, why not use:
An optional destructor part can be used for further cleanup (remove
listeners etc.)
Which can
syd sandy wrote:
Does yasims 'approach aoa ' mean angle of decsent path or pitch of
the aircraft? Ive always assumed it the angle of approach path.
Neither. The acronym AoA is used in place of angle of attack,
which is a technical term referring to the angle with which the airflow
meets the
Frederic Bouvier wrote:
Melchior FRANZ wrote:
Why the #ifdef? Is there a reasonable case where CONFIG_H is *not*
available?
It has always been the practice to enclose #include config.h by
#ifdef HAVE_CONFIG_H from the beginning of autoconf/automake.
That's not really an answer to the
Mathias Frölich wrote:
Because that is the way automake is supposed to work. You can
either include all defines autoconf generates in the compilers
commandline, then HAVE_CONFIG_H is not defined or autoconf puts the
defines into config.h and defines HAVE_CONFIG_H ...
What's wrong with just
Christian Mayer wrote:
So to stay portable it's a must - you are including a file that does
not exist otherwise.
Again: just stub out an empty config.h and check it in. Will this not
work on MSVC for some reason? Note that all other platforms are Unix
and use autotools, MSVC is the only one
dene maxwell wrote:
Doesn't make the least sense sorry don't understand this
... Telenet being a application layer protocol requires alot more details as
to recipient and also alot higher overhead to implement...whereas UDP being
a trasport layer protocol is less distinct in is
Melchior FRANZ wrote:
My little Nasal console:
http://members.aon.at/mfranz/nasal-console.jpg [23 kB]
Nice. :) I get all teary-eyed when I see stuff like this.
Andy
---
This SF.net email is sponsored by: Splunk Inc. Do you grep
Justin Smithies wrote:
I would like an option to be added to the FG command line that would
remove so much of the screen on the right so where my two monitors
join its like having the window strut seperators.
You'd be better off just running a separate FlightGear instance on the
second monitor
Justin Smithies wrote:
I'm using a dual nvidia 5200 and i have setup twin view. If i run
FG in a window i can get it to fill the 2 screens but i want to use
full screen and if i do that it only goes on the 1st screen.
That's more of a Glut/SDL limitation. Choosing full screen just
forwards
alexis bory wrote:
Did anybody asked about a way to keep the hud's marks inside the hud
screen ?
There isn't a good way to do it right now. The current HUD code is
very old, and predates the 3D cockpits. It just draws directly to the
screen (with a matrix hack to make it appear in the correct
Melchior FRANZ wrote:
I've yesterday committed a Nasal class that helps to display log
information in a scrolling transparent window. This can be used for
ATC message type of information and whatever info you want to
display.
This is really slick. How about porting the existing screenPrint()
Josh Babcock wrote:
We use one prop /controls/gear/gear-down to denote when gear is down
and locked. does YASim just turn on the extra drag when that changes
to 1 or does it slowly increase it over the time of extension?
It's smoothly interpolated across the extension.
Andy
Drew wrote:
If I may elaborate on this problem, most of the string handling
routines (strcpy, strcat, sprintf...etc.) have a more 'managed'
alternative that Microsoft encourages programmers to use. These
have the '_s' after them (strcpy_s, strcat_s, sprintf_s), and
contain an additional
Vance Souders wrote:
Microsoft has made major changes to the standard C++ and C
runtime libraries under Visual Studio 2005. When compiling
Flightgear 0.9.9 under VS 2005, you get about 2500 deprecated
function warnings because of these changes. So, to build FG
under VS 05 with zero errors
Frederic Bouvier wrote:
It says that strcpy ( for instance ) is not secure and one should
use strcpy_s that is the secured version. Maybe I missed something,
but I don't thing strcpy_s is available outside the MS world.
They couldn't just implement strncpy ... ? Still, that's a good
example
Curtis L. Olson wrote:
Is there a way in nasal to read the contents of a file or list the
contents of a directory?
Ideally I would like to list all the contents of a directory and build
an array of file names found (and do this in nasal.)
Is there a way to do this?
I have a
I wrote:
Maybe someone could hook the plib directory stuff into NasalSys.cxx?
My build tree is ancient, so I don't quite have enough time to test
this (or even try to compile it). But this is the basics of how it
would work: insert this into NasalSys.cxx and add an entry to the
funcs[] table
101 - 119 of 119 matches
Mail list logo
