Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Norman Vine writes: > It would be nice if had a 'lint' like XML checker for all of the > 'properties' We get an error if the XML document is not well-formed, but not if there is an unrecognized property. There are lots of good reasons for keeping it that way. > Anyone know of an OpenSource alternative to XMLSpy Tons -- nearly all good XML software is open source. The problem would be writing and maintaining DTDs or schemas for all our possible information variants. I've worked on a lot of SGML and XML systems, and I've seen people spend a lot of money on that approach, but I've never seen them get any substantial benefit from it. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David Megginson writes: > > There was a typo "bindings" instead of "binding" -- it's fixed now. > It would be nice if had a 'lint' like XML checker for all of the 'properties' Anyone know of an OpenSource alternative to XMLSpy Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David Megginson writes: > > Do the > > LatLonFormatToggle > > or the > > AutoPilotAdjuster > > > > Work for anybody ??? > > I'll try to hunt down the problem with these. There was a typo "bindings" instead of "binding" -- it's fixed now. Thanks, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Norman Vine writes: > Do the > LatLonFormatToggle > or the > AutoPilotAdjuster > > Work for anybody ??? I'll try to hunt down the problem with these. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Michael Basler writes: > > What versions of plib and G++ are you using? > > PLIB CVS as of today. GCC 2.95. I have a guess about what the problem might be -- it could be an STL problem in 2.95. If so, I should be able to work around it. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David, > What versions of plib and G++ are you using? PLIB CVS as of today. GCC 2.95. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Do the
LatLonFormatToggle
or the
AutoPilotAdjuster
Work for anybody ???
FWIW I added some printfs() and it does not appear if either
of their 'launchers' is ever fired()
Note:
The AddWayPoint and PopWayPoint 'launchers' do print
their debug messages
Norman
extern void AddWayPoint (puObject *);
static bool
do_ap_add_waypoint_dialog (const SGPropertyNode * arg)
{
cout << "do_ap_add_waypoint_dialog" << endl;
AddWayPoint(0);
return true;
}
extern void PopWayPoint (puObject *);
static bool
do_ap_pop_waypoint_dialog (const SGPropertyNode * arg)
{
cout << "do_ap_pop_waypoint_dialog" << endl;
PopWayPoint(0);
return true;
}
extern void fgAPAdjust (puObject *);
static bool
do_ap_adjust_dialog (const SGPropertyNode * arg)
{
cout << "do_ap_adjust_dialog" << endl;
fgAPAdjust(0);
return true;
}
extern void fgLatLonFormatToggle (puObject *);
static bool
do_lat_lon_format_dialog (const SGPropertyNode * arg)
{
cout << "do_lat_lon_format_dialog" << endl;
fgLatLonFormatToggle(0);
return true;
}
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
From: "Michael Basler" <[EMAIL PROTECTED]> > Curt, > > > With the new "Air" dialog box, I'm running into a segfault. What I do > > to trigger the crash is first bringe up the "Air" dialog box, then I > > examine the data and decide I don't want to change anything, then I > > click ok. > ... > > Seems to double my observation. Obviously it's not a Cygwin thingy, as I > supposed at first. I am not seeing that with my MSVC build. I can see the weather boxes and click on OK without problems. But (see my previous post) there is a function that needs a return value. I added 'return false;' to fireItem in FGMenuBar and perhaps this is your problem with gcc. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Michael Basler writes: > > With the new "Air" dialog box, I'm running into a segfault. What I do > > to trigger the crash is first bringe up the "Air" dialog box, then I > > examine the data and decide I don't want to change anything, then I > > click ok. > ... > > Seems to double my observation. Obviously it's not a Cygwin thingy, as I > supposed at first. What versions of plib and G++ are you using? Thanks, and all the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
Curtis L. Olson writes: > With the new "Air" dialog box, I'm running into a segfault. What I do > to trigger the crash is first bringe up the "Air" dialog box, then I > examine the data and decide I don't want to change anything, then I > click ok. > > > The back trace lists a bunch of internal PUI calls and then dies in > GUI/dialog.cc:action_callback(), specifically at line #24. I'm > guessing that info->bindings[i] doesn't have a valid object so when it > tries to call the fire() method it segfaults. > > Is that enough for you to go on, or should I dig deeper and find > additional info for you? > > I'm getting this exact same behavior all three weather dialog boxes. I can guess at a couple of possibilities -- first, if you're using G++ 2.95, the STL stuff could be broken somehow; and second, if you're using plib 1.6 rather than the CVS head, there could be a bug with the userdata that was fixed later. Could you add a few print statements around the problem line and let me know what you see? Thanks, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Curt, > With the new "Air" dialog box, I'm running into a segfault. What I do > to trigger the crash is first bringe up the "Air" dialog box, then I > examine the data and decide I don't want to change anything, then I > click ok. ... Seems to double my observation. Obviously it's not a Cygwin thingy, as I supposed at first. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
David, With the new "Air" dialog box, I'm running into a segfault. What I do to trigger the crash is first bringe up the "Air" dialog box, then I examine the data and decide I don't want to change anything, then I click ok. The back trace lists a bunch of internal PUI calls and then dies in GUI/dialog.cc:action_callback(), specifically at line #24. I'm guessing that info->bindings[i] doesn't have a valid object so when it tries to call the fire() method it segfaults. Is that enough for you to go on, or should I dig deeper and find additional info for you? I'm getting this exact same behavior all three weather dialog boxes. Thanks, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
Curtis L. Olson writes: > I'm not sure your thinking on this, but the "Reset" option has > disappeared. That's kind of nice if you want to do a complete reset > of everything. I put the support in C++, but left it out of the XML by accident. It's there now. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
Bernie Bright writes: > The weather dialogs are not found unless the FG_ROOT environment variable is > set. Shouldn't this really be globals->get_fg_root() ? Good catch, thanks. It's fixed now. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
David, I'm not sure your thinking on this, but the "Reset" option has disappeared. That's kind of nice if you want to do a complete reset of everything. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
Bernie Bright writes: > On Sat, 18 Jan 2003 12:39:32 -0500 > David Megginson <[EMAIL PROTECTED]> wrote: > > > The new XML-configured menubar is now the default for FlightGear; > > configure --with-old-menubar to get the old one (which I'll keep > > around for now, until we're sure the new one is working OK). > > > > Please, everyone, give the new menubar a spin, and take a look at > > $FG_ROOT/gui/menubar.xml and $FG_ROOT/gui/dialogs/*.xml to see how to > > add new menu entries and dialogs. As an example, I've added a > > "Weather" menu with the ability to set winds, > > temperature/pressure/dewpoint, and cloud layers. > > > > The weather dialogs are not found unless the FG_ROOT environment variable is > set. Shouldn't this really be globals->get_fg_root() ? Ahhh, that would explain why I haven't been able to get them to work yet. Yes, if we stay with the way we have been doing this, we should look for files relative to globals->get_fg_root() since you can specify the root via command line options and probably via properties somehow too. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds,winds, and air
On Sat, 18 Jan 2003 12:39:32 -0500 David Megginson <[EMAIL PROTECTED]> wrote: > The new XML-configured menubar is now the default for FlightGear; > configure --with-old-menubar to get the old one (which I'll keep > around for now, until we're sure the new one is working OK). > > Please, everyone, give the new menubar a spin, and take a look at > $FG_ROOT/gui/menubar.xml and $FG_ROOT/gui/dialogs/*.xml to see how to > add new menu entries and dialogs. As an example, I've added a > "Weather" menu with the ability to set winds, > temperature/pressure/dewpoint, and cloud layers. > The weather dialogs are not found unless the FG_ROOT environment variable is set. Shouldn't this really be globals->get_fg_root() ? Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Michael Basler writes: > > > That looks like it's just program output. Can you get a proper > > backtrace in gdb or some other debugger? > > This would imply me knowing how to use it. I am not a programmer, just an > ordinary poor physicist... > > I analyzed a core file with gdb once. However, FG doesn't dump a core file > today. Here's a file fgfs.exe.stackdump it creates: > Can you tell me how to analyse this using gdb? (Which btw. is a graphical > fronent for Cygwin by default which, however, can be switched off.) Michael ehat is the output of this command note you will need the full path to fgfs.exe and this is all one line Norman addr2line -f -e fgfs.exe 0x007251A7 0x08CA3C8 0x08CADBC 0x08CE6A4 0x08C68BB 0x08C68BB 0x08C5E57 0x074DCF9 0x075776A 0x000CE6A 0x7D37AD7 0x7D3CCD4 0x7D15CD6 0x7D23346 0xF0F2CCF 0x7D37AD7 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Curt, David
I already messed a bit around with gdb, but it always died. Mean issue was I
set --fg_root= instead of fg-root= :-(((
It now does run. However, after selecting the button in question, flightgear
never dies completely. Instead, it hangs infinitely. I had to kill it
manually.
The trace did not say much
$ where
__:
not
found
This: not found
__:
not
found
The: not found
http://www.cdrom.com/pub/infozip/doc/WHERE: not found
Note: not found
and: not found
/cygdrive/c/bin/where: 12: Syntax error: word unexpected (expecting ")")
-
However, I made another run using the graphical GDB frontend. FG hangs
again, but I find from the graphical window it's in dialog.cxx, line 26
(something with the new GUI). Maybe this helps:
--
- 23->get_group(FGSubsystemMgr::INIT)->get_subsystem("gui");
- 24 gui->setCurrentWidget(info->widget);
- 25 for (int i = 0; i < info->bindings.size(); i++)
- 26 info->bindings[i]->fire();
- 27 gui->setCurrentWidget(0);
--
Regards, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Typically you run fgfs from within gdb. Something like bash$ gdb fgfs gdb> run --fgfs-option1 --fgfs-option2 Then when you get a crash you can type: gdb> where To get a back trace. Regards, Curt. Michael Basler writes: > David, > > > That looks like it's just program output. Can you get a proper > > backtrace in gdb or some other debugger? > > This would imply me knowing how to use it. I am not a programmer, just an > ordinary poor physicist... > > I analyzed a core file with gdb once. However, FG doesn't dump a core file > today. Here's a file fgfs.exe.stackdump it creates: > > > Exception: STATUS_ACCESS_VIOLATION at eip=007251A7 > eax=1925FB78 ebx=0003 ecx=0039 edx=19194DD0 esi=19194DD8 > edi=17F81410 > ebp=0022EC74 esp=0022EC20 > program=G:\cygwin\usr\local\flightgear\BIN\fgfs.exe > cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 > Stack trace: > Frame Function Args > 0022EC74 007251A7 (19194BF0, 0001, 0022ECA4, 008CA36F) > 0022ECA4 008CA3C8 (19194BF0, , 0001, 001D) > 0022ECE4 008CADBC (19194BF0, , 0001, 001D) > 0022ED24 008CE6A4 (19194BF0, , 0001, 001D) > 0022ED74 008C68BB (19255768, , 0001, 0155) > 0022EDC4 008C68BB (1777DC70, , 0001, 0155) > 0022EE14 008C5E57 (, 0001, 0155, 0119) > 0022EFB4 0074DCF9 (1866B330, , 0001, 0155) > 0022EFE4 0075776A (, 0001, 0155, 0119) > 0022F108 1000CE6A (001206E6, 0202, , 01190155) > 0022F134 77D37AD7 (1000C0E7, 001206E6, 0202, ) > 0022F19C 77D3CCD4 (, 1000C0E7, 001206E6, 0202) > 0022F1CC 77D15CD6 (0823, 001206E6, 0202, ) > 0022F1EC 77D23346 (0823, 001206E6, 0202, ) > 0022F22C 5F0F2CCF (001206E6, 0202, , 01190155) > 0022F258 77D37AD7 (5F0F2AB6, 001206E6, 0202, ) > End of stack trace (more stack frames may be present) > > > Can you tell me how to analyse this using gdb? (Which btw. is a graphical > fronent for Cygwin by default which, however, can be switched off.) > > Regards, Michael > > > > > > > > > > -- > Michael Basler, Jena, Germany > [EMAIL PROTECTED] > http://www.geocities.com/pmb.geo/ > > > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David, > That looks like it's just program output. Can you get a proper > backtrace in gdb or some other debugger? This would imply me knowing how to use it. I am not a programmer, just an ordinary poor physicist... I analyzed a core file with gdb once. However, FG doesn't dump a core file today. Here's a file fgfs.exe.stackdump it creates: Exception: STATUS_ACCESS_VIOLATION at eip=007251A7 eax=1925FB78 ebx=0003 ecx=0039 edx=19194DD0 esi=19194DD8 edi=17F81410 ebp=0022EC74 esp=0022EC20 program=G:\cygwin\usr\local\flightgear\BIN\fgfs.exe cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022EC74 007251A7 (19194BF0, 0001, 0022ECA4, 008CA36F) 0022ECA4 008CA3C8 (19194BF0, , 0001, 001D) 0022ECE4 008CADBC (19194BF0, , 0001, 001D) 0022ED24 008CE6A4 (19194BF0, , 0001, 001D) 0022ED74 008C68BB (19255768, , 0001, 0155) 0022EDC4 008C68BB (1777DC70, , 0001, 0155) 0022EE14 008C5E57 (, 0001, 0155, 0119) 0022EFB4 0074DCF9 (1866B330, , 0001, 0155) 0022EFE4 0075776A (, 0001, 0155, 0119) 0022F108 1000CE6A (001206E6, 0202, , 01190155) 0022F134 77D37AD7 (1000C0E7, 001206E6, 0202, ) 0022F19C 77D3CCD4 (, 1000C0E7, 001206E6, 0202) 0022F1CC 77D15CD6 (0823, 001206E6, 0202, ) 0022F1EC 77D23346 (0823, 001206E6, 0202, ) 0022F22C 5F0F2CCF (001206E6, 0202, , 01190155) 0022F258 77D37AD7 (5F0F2AB6, 001206E6, 0202, ) End of stack trace (more stack frames may be present) Can you tell me how to analyse this using gdb? (Which btw. is a graphical fronent for Cygwin by default which, however, can be switched off.) Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Michael Basler writes: > One issue: When I make a selection from the Weather menu the dialog box > opens as it should. However, after only pressing either OK or Cancel the > simulator silently dies with a stackdump as follows: > > _ > token = OBJECT_BASE name = 942035.btg > load() base = ./Scenery > Loading tile ./Scenery/w130n30/w123n37/942067 > token = OBJECT_BASE name = 942067.btg > token = OBJECT name = 59CA.btg > 5 [main] FGFS 4012 handle_exceptions: Exception: > STATUS_ACCESS_VIOLATION >5512 [main] FGFS 4012 open_stackdumpfile: Dumping stack trace to > fgfs.exe.sta > ckdump > _ That looks like it's just program output. Can you get a proper backtrace in gdb or some other debugger? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David, here's a report from a guinea pig. Recent CVS code including XML menu stuff compiles and runs fine on a Windows/Cygwin system with GCC2.95. I am really glad someone started to work on it. Hopefully, we can reduce the command line options to nearly zero. We'll gratefully add the new menu entries to the docs and delete menu options for them :-). One issue: When I make a selection from the Weather menu the dialog box opens as it should. However, after only pressing either OK or Cancel the simulator silently dies with a stackdump as follows: _ token = OBJECT_BASE name = 942035.btg load() base = ./Scenery Loading tile ./Scenery/w130n30/w123n37/942067 token = OBJECT_BASE name = 942067.btg token = OBJECT name = 59CA.btg 5 [main] FGFS 4012 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 5512 [main] FGFS 4012 open_stackdumpfile: Dumping stack trace to fgfs.exe.sta ckdump _ Any idea? Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
Curtis L. Olson writes: > One thing I'd like to have is a --disable-menu/--enable-menu option so > that we can have the menu start off by default if we want. Yes, I need to reinstate show/hide menu -- thanks for the reminder. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ANN: New Menu Bar; dialogs for clouds, winds, and air
David Megginson writes: > The new XML-configured menubar is now the default for FlightGear; > configure --with-old-menubar to get the old one (which I'll keep > around for now, until we're sure the new one is working OK). > > Please, everyone, give the new menubar a spin, and take a look at > $FG_ROOT/gui/menubar.xml and $FG_ROOT/gui/dialogs/*.xml to see how to > add new menu entries and dialogs. As an example, I've added a > "Weather" menu with the ability to set winds, > temperature/pressure/dewpoint, and cloud layers. > > Also, what areas have the most pressing need for menu entries and > dialogs now? We should try to start with the most urgent cases and > then work our way down. > > Coming next: sliders, checkboxes, pick/combo-boxes, and other widgets > to make dialogs friendlier to use. David, Thanks for working on this ... great news! One thing I'd like to have is a --disable-menu/--enable-menu option so that we can have the menu start off by default if we want. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
