Julian Foad wrote:
> Well, I'll put it this way: If I turn the 2D panel on and off with "P"
> while flying "--aircraft=c172-3d", and note where a particular button
> is, and then turn it off so that only the 3D panel is visible, I can
> still click where the 2D button was as well as where the 3D button is
> visible.
Heh, hard to argue with that. Indeed, there was no check for panel
visibility in the input code. I guess we've never noticed because
nothing was fighting for the same real estate in the past. This
one-liner appears to fix the problem.
And, since you were right, good catch. :)
Andy
RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Input/input.cxx,v
retrieving revision 1.4
diff -u -r1.4 input.cxx
--- src/Input/input.cxx 29 Oct 2002 19:44:03 -0000 1.4
+++ src/Input/input.cxx 5 Nov 2002 01:38:23 -0000
@@ -379,6 +379,7 @@
if (puMouse(b, updown, x, y))
return;
else if ((current_panel != 0) &&
+ current_panel->getVisibility() &&
current_panel->doMouseAction(b, updown, x, y))
return;
else if (fgHandle3DPanelMouseEvent(b, updown, x, y))
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
