From: "Jonathan Polley" <[EMAIL PROTECTED]>
> I updated to the latest CVS for both FlightGear and the base packages
> and am having a problem under Windows (MacOS X is working correctly).
> The module src/new_gui.cxx runs and starts reading the XML files but
> starts getting into trouble. I g
I updated to the latest CVS for both FlightGear and the base packages
and am having a problem under Windows (MacOS X is working correctly).
The module src/new_gui.cxx runs and starts reading the XML files but
starts getting into trouble. I get the following errors printed to the
screen
Error
David Luff writes:
>>
> A couple of points I noticed are that when sliding the mouse sideways
> across the menubar at the top, the original submenu is not replaced by the
> next ones,
I believe that this is a dsign decision in PLIB
It is related to being able to keep focus on a slider or a dial
David Megginson writes:
>
> David Luff writes:
>
> > A couple of points I noticed are that when sliding the mouse sideways
> > across the menubar at the top, the original submenu is not replaced by the
> > next ones, and pressing escape when a dialog with a cancel box is displayed
> > still br
On 1/19/03 at 7:51 PM David Megginson wrote:
>It may have to do with whether or not the dialog is modal. I'll have
>to experiment a bit.
>
>Did the old dialogs close when you pressed ESC?
No, the old behaviour was just the same, it was something I never got round
to mentioning...
Cheers - Dave
David Luff writes:
> A couple of points I noticed are that when sliding the mouse sideways
> across the menubar at the top, the original submenu is not replaced by the
> next ones, and pressing escape when a dialog with a cancel box is displayed
> still brings up the exit sim dialog instead of
On 1/19/03 at 7:01 PM David Megginson wrote:
>Michael Basler writes:
>
> > Could we draw the menu line over the full width, independent of
> > resolution? This is common for nearly all programs on all
> > platforms I know.
>
>Right now we're using the higher-level PUI menubar widget, so we have
>
From: "Frederic Bouvier" <[EMAIL PROTECTED]>
> I am fighting against a memory corruption for 2 hours and I solved it.
> Not enought room was allocated in ATCmgr.cxx and auto_gui.cxx to store
> strings.
> Here is the patch, hoping it will solve Curt's and Michael's problems :
Dave already patched
Michael Basler writes:
> Could we draw the menu line over the full width, independent of
> resolution? This is common for nearly all programs on all
> platforms I know.
Right now we're using the higher-level PUI menubar widget, so we have
to take what we get. To change its appearance, we'd h
Curtis L. Olson writes:
> > How would people feel about going opaque?
>
> What about 90% opaque? Just enough to say, "yeah, we're cool" but for
> all practical purposes, they are opaque ... (?)
Sounds like a good compromise.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], h
David,
After getting recent CVS updates the menu crash is gone for me too. Great
Work you guys!
Regards, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
___
Flightgear-devel
David,
> The translucent dialogs we've been using look very spiffy, but it
> turns out that they're not all that practical once you start using
> things like pop-up menus in combo boxes. Take a look at the clouds
> dialog in the latest CVS (FlightGear and base package) to see why.
>
> How would p
David Megginson writes:
> The translucent dialogs we've been using look very spiffy, but it
> turns out that they're not all that practical once you start using
> things like pop-up menus in combo boxes. Take a look at the clouds
> dialog in the latest CVS (FlightGear and base package) to see why.
On 1/19/03 at 6:06 PM David Megginson wrote:
>The translucent dialogs we've been using look very spiffy, but it
>turns out that they're not all that practical once you start using
>things like pop-up menus in combo boxes. Take a look at the clouds
>dialog in the latest CVS (FlightGear and base pa
David Megginson writes:
> The translucent dialogs we've been using look very spiffy, but it
> turns out that they're not all that practical once you start using
> things like pop-up menus in combo boxes. Take a look at the clouds
> dialog in the latest CVS (FlightGear and base package) to see why.
The translucent dialogs we've been using look very spiffy, but it
turns out that they're not all that practical once you start using
things like pop-up menus in combo boxes. Take a look at the clouds
dialog in the latest CVS (FlightGear and base package) to see why.
How would people feel about go
Curtis L. Olson writes:
> I still haven't figured out the code, but is one of the call backs
> deleting the dialog box?
That might be it -- try dropping this in instead:
/**
* Action callback.
*/
static void
action_callback (puObject * object)
{
GUIInfo * info = (GUIInfo *)object->getUse
Exhibition of mock-up wooden Wright Flyer cockpit attached to MSFS visuals:
http://www.eaa.org/communications/eaanews/030117_simulator.html
Cheers - Dave
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo
Curtis L. Olson writes:
> For what it's worth, the "Apply" button seems to work (and triggers
> one "fire()" call, but the "OK" button triggers 2 fire() calls and
> then the size of the vector get's corrupted.
>
> The "Cancel" button also causes a crash. It makes 1 fire() call,
> corrupts the v
Frederic Bouvier writes:
> My new option parsing function is also working. You will receive it
> soon.
I've got it, and will take a look as soon as I'm done rebuilding with
3.2.
Thanks,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
_
David Megginson writes:
> Curtis L. Olson writes:
>
> > What compiler options do you build with? I usually override the
> > default and build with -Wall -O2, I'll do a rebuild with default
> > options and see if that helps.
>
> With 3.2, I usually build with
>
> -g -O1 -finline-limit=6 -f
On 1/19/03 at 10:09 PM Frederic Bouvier wrote:
>I am fighting against a memory corruption for 2 hours and I solved it.
>Not enought room was allocated in ATCmgr.cxx and auto_gui.cxx to store
>strings.
>Here is the patch, hoping it will solve Curt's and Michael's problems :
>
Oops, sorry.
I've co
From: "David Megginson" <[EMAIL PROTECTED]>
> Frederic Bouvier writes:
>
> > I am fighting against a memory corruption for 2 hours and I solved it.
> > Not enought room was allocated in ATCmgr.cxx and auto_gui.cxx to store
> > strings.
>
> I'll cross my fingers.
>
> Frederic -- are the XML d
Frederic Bouvier writes:
> I am fighting against a memory corruption for 2 hours and I solved it.
> Not enought room was allocated in ATCmgr.cxx and auto_gui.cxx to store
> strings.
I'll cross my fingers.
Frederic -- are the XML dialogs still working OK for you?
All the best,
David
--
D
Curtis L. Olson writes:
> I think that something is stomping on the memory occupied by the
> vector. That's the only way I can explain it's size getting
> corrupted. There's so many levels of indirection though it's
> difficult to trace back what's going on where. I'm willing to help
> tra
Curtis L. Olson writes:
> What compiler options do you build with? I usually override the
> default and build with -Wall -O2, I'll do a rebuild with default
> options and see if that helps.
With 3.2, I usually build with
-g -O1 -finline-limit=6 -finline-functions
For the 2.95 test, howev
I am fighting against a memory corruption for 2 hours and I solved it.
Not enought room was allocated in ATCmgr.cxx and auto_gui.cxx to store
strings.
Here is the patch, hoping it will solve Curt's and Michael's problems :
D:\FlightGear\cvs\FlightGear\src>cvs -z3 -q diff -u ATC/ATCmgr.cxx
Autopilo
Bert Driehuis writes:
> On Sun, 19 Jan 2003, David Megginson wrote:
>
> > > So, I can report the current CVS snapshot works on FreeBSD 4.7 with the
> > > autoconf patches in my previous post.
> >
> > Excellent. Which version of G++ did you use?
>
> Sorry for not mentioning that -- I specifical
David Megginson writes:
> OK, guess #1 is down the tubes. I'm going to need help with this one,
> because the bug does not occur with G++ 3.2 no matter how many times I
> try it, and it apparently does not occur with MSVC++ either.
>
> Curt and Michael: has either of you tried a
>
> make clea
Norman Vine writes:
> What I would like is a way to define menus something like
>
> myMenu = (
> ('&File',
> ('New', (ALT, 'N'), self.OnFileNew),
> ('Open', (ALT, 'O'), self.OnFileOpen),
> ('Close', (ALT, 'C'), self.OnFileClose)),
> ('&Edit',
>
On Sun, 19 Jan 2003, David Megginson wrote:
> > So, I can report the current CVS snapshot works on FreeBSD 4.7 with the
> > autoconf patches in my previous post.
>
> Excellent. Which version of G++ did you use?
Sorry for not mentioning that -- I specifically checked it with the
intent of shari
Assuming you just changed i++ to ++i, no difference.
Curt.
Norman Vine writes:
> Curtis L. Olson writes:
> >
> > I put in a printf and I see that, well, ok, this is strange (or I
> > haven't had enough caffeine yet ...)
> >
> > I added the following cout's:
> >
> > cout << "size = " << inf
I just did a very time-consuming rebuild plib, Metakit, SimGear, and
FlightGear from scratch with G++ 2.95 instead of 3.2, and I'm still
not having any problem with the XML-configured dialog boxes. In case
it's helpful, here's an ldd from the 2.95-built binary:
libmk4.so.0 => /usr/local/l
David Megginson writes:
>
> map > _bindings;
>
> p.s. Now why do I prefer coding in Java, again?
What I would like is a way to define menus something like
myMenu = (
('&File',
('New', (ALT, 'N'), self.OnFileNew),
('Open', (ALT, 'O'), self.OnFileOpen),
('Close',
Bert Driehuis writes:
> So, I can report the current CVS snapshot works on FreeBSD 4.7 with the
> autoconf patches in my previous post.
Excellent. Which version of G++ did you use?
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
_
Curtis L. Olson writes:
>
> I put in a printf and I see that, well, ok, this is strange (or I
> haven't had enough caffeine yet ...)
>
> I added the following cout's:
>
> cout << "size = " << info->bindings.size() << endl;
> for (int i = 0; i < info->bindings.size(); i++) {
> cout
Follow up to self:
> Todays CVS snapshot of FlightGear crashes in the new XML menu stuff;
> haven't investigated yet where menubar.xml is supposed to come from
> (just joined the list).
Hm. It helps to not just download, but also install, the updated
fgfs_base :-)
So, I can report the curren
The attached diffs (relative to todays CVS) detect pthreads on FreeBSD.
Even when the app itself doesn't need threading, any app linked against
Mesa must by compile with "g++ -pthread" (otherwise, "gssInit called
without valid rendering context" rears its ugly but helpful head).
The checks only ki
Michael Basler writes:
> I updated to the latest CVS and rebuilt, but it still dies in the
> dialogue with "OK" etc..
>
> Sorry, Michael
OK, guess #1 is down the tubes. I'm going to need help with this one,
because the bug does not occur with G++ 3.2 no matter how many times I
try it, and i
David,
I updated to the latest CVS and rebuilt, but it still dies in the dialogue
with "OK" etc..
Sorry, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
___
Flightgear-devel
I've checked in a possible fix for G++ 2.95 -- please let me know if
it works.
I've also made some GUI enhancements:
1. Added checkboxes for boolean properties.
2. Automatically update after "apply" to see what really got into the
property tree.
3. Use plib's ability to beautify numbers.
A
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 a
Frederic Bouvier writes:
> > Would you like to take a stab at it?
>
> OK, I'll take this one.
Great -- thanks.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
___
Flightgear-devel mailing list
[EMAIL PROTE
Curtis L. Olson writes:
> So this looks wierd ... something in the fire() method appears to be
> stomping on the bindings vector? The size jumps from 2 up to
> 767087068. This smells a little like some sort of memory corruption
> or buffer overrun someplace
The fire() method has no
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
___
Flight
From: "David Megginson" <[EMAIL PROTECTED]>
> Frederic Bouvier writes:
>
> > I also have a problem where options.cxx has too many levels of
imbrication
> > in parse_option (max is 128). There are too many 'else if' construct.
> > Can we think about another scheme to parse options (iterating on
FYI
While some were marching yesterday
I helped celebrate one of man's greatest gadgets
http://dev.communicom.net/marconi/index.html
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-de
David Megginson writes:
> I've been trying to hunt down why G++ 2.95/Cygwin might be having a
> runtime problem with menubar.[ch]xx. Could this line from menubar.hxx
> be causing the problem?
>
> map > _bindings;
>
> It is proper ANSI C++, and neither G++ 3.2 nor MSVC++ seems to have
> any pro
On 1/19/03 at 8:37 AM Curtis L. Olson wrote:
>With recent code changes, I'm seeing a significant pause in the
>animation about every 2 seconds. This is enough to create a break in
>the audio with every pause. I don't think this is just my machine.
>Is any one else seeing this in the latest CVS?
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, [EM
Frederic Bouvier writes:
> I also have a problem where options.cxx has too many levels of imbrication
> in parse_option (max is 128). There are too many 'else if' construct.
> Can we think about another scheme to parse options (iterating on an array or
> an XML file) ?
The 128 hard-coded limi
> With recent code changes, I'm seeing a significant pause in the
> animation about every 2 seconds. This is enough to create a break in
> the audio with every pause. I don't think this is just my machine.
> Is any one else seeing this in the latest CVS? If it's not just me,
> we need to track
David Megginson writes:
>>
> It is proper ANSI C++, and neither G++ 3.2 nor MSVC++ seems to have
> any problem with it, but perhaps G++ 2.95 in Linux or Cygwin isn't
> initializing the vector properly
It is quite easy to check code for portability between libStdC++ versions
http://gcc.gnu.org/fo
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/
___
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 PR
From: "David Megginson" <[EMAIL PROTECTED]>
> Frederic Bouvier writes:
>
> > MSVC says that 'FGMenuBar::fireItem (puObject * item)' in
menubar.cxx(335)
> > is missing a return value and I am afraid it is right.
>
> Quite right -- I'll change its return value to void and check in a
> fixed versio
I've been trying to hunt down why G++ 2.95/Cygwin might be having a
runtime problem with menubar.[ch]xx. Could this line from menubar.hxx
be causing the problem?
map > _bindings;
It is proper ANSI C++, and neither G++ 3.2 nor MSVC++ seems to have
any problem with it, but perhaps G++ 2.95 in Li
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 mail
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
Frederic Bouvier writes:
> MSVC says that 'FGMenuBar::fireItem (puObject * item)' in menubar.cxx(335)
> is missing a return value and I am afraid it is right.
Quite right -- I'll change its return value to void and check in a
fixed version of menubar.[ch]xx.
Unfortunately, that problem wouldn'
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.
> ...
>
>
Michael Basler writes:
> > With recent code changes, I'm seeing a significant pause in the
> > animation about every 2 seconds. This is enough to create a break in
> > the audio with every pause. I don't think this is just my machine.
> > Is any one else seeing this in the latest CVS? If it
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 obse
From: "Curtis L. Olson" <[EMAIL PROTECTED]>
> With recent code changes, I'm seeing a significant pause in the
> animation about every 2 seconds. This is enough to create a break in
> the audio with every pause. I don't think this is just my machine.
> Is any one else seeing this in the latest CV
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 in
MSVC says that 'FGMenuBar::fireItem (puObject * item)' in menubar.cxx(335)
is missing a return value and I am afraid it is right.
Cheers,
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear
Curt,
> With recent code changes, I'm seeing a significant pause in the
> animation about every 2 seconds. This is enough to create a break in
> the audio with every pause. I don't think this is just my machine.
> Is any one else seeing this in the latest CVS? If it's not just me,
> we need to
With recent code changes, I'm seeing a significant pause in the
animation about every 2 seconds. This is enough to create a break in
the audio with every pause. I don't think this is just my machine.
Is any one else seeing this in the latest CVS? If it's not just me,
we need to track down where
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 t
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/
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
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/
___
Ima Sudonim writes:
> Is the new version of PLIB required or optional for the fg source
> downloaded from cvs by the latest changes? Are there any changes to
> the SL directory that are required by flightgear?
The CVS version of plib is optional, but you won't get scripting
support without
73 matches
Mail list logo
