This error has been fixed in CVS. MSVC6 is not able to choose between two
member functions, one const and the other not const, so you have to cast
the 4th argument :
PropertyManager-Tie(atmosphere/p-turb-rad_sec, this,1,
FGAtmosphere::GetTurbPQR);
becomes:
Norman Vine writes:
FWIW - What I think would likely be the 'pentultimate' system is a Tool
that read the existing XML configuration files and automagically created
a GUI from what it found. This is sort of what the HTML interface to the
properties does now
If the GUI is able to run
Norman Vine writes:
but this was in reference to 'ease of use' for 'users' not 'developers'
hmmm
maybe FlightGear 'users' all know how to run compilers :-))
No, but any ones who can write Python or Java code certainly can. A
user-friendly, extensible GUI would probably have a
I've updated the --wind=DIR@SPEED option to allow a range for DIR or
SPEED. For example, winds from 180 degrees at 10 knots gusting 15
knots would be
--wind=180@10:15
I haven't had the chance to add variable wind direction to
FGEnvironment yet, but the option will be accepted:
Norman Vine [EMAIL PROTECTED] said:
My point was that the beauty of having a 'scriptable' GUI was that a
user, not a developer / programmer, should be able to personalize
their GUI easily, not so sure this would be possible with a C++ GUI.
Well one time I was asked to write an xml
Thanks, Fred.
I have downloaded the CVS version now, and as you said this has been fixed.
However, I get a lot of link errors when I compile flightgear (simgear cvs
compiled fine). Do I have to be aware where to put the plib and simgear
libs? Or are the incompatibilities between version, eg
Hi,
Just wanted to let you know that I haven't disappeared. I've been quite
busy at work the last two weeks and haven't had a lot of free time. I'm
shooting for posting a new Windows alpha executable and a tar of the
source
presuming Linux is building ok this weekend.
Any news on your
