Andy Ross 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. Clicking in either place has the same result of activating the feature. As I said, if the position of one of these invisible 2D hot-spots obscures a 3D hot-spot, then the 3D one appears not to be working, until you change view direction a bit or zoom so it is in a different area of the screen.Julian Foad wrote: > For those who were wondering why it seems intermittently broken, what > seems to be happening is the 2D panel hotspots are always active as > well, and they pick up the mouse clicks as well (or instead, if the 2D > hotspot area overlaps a 3D hotspot area).Are you sure? I thought this might be it too, and tried tracking it down. The 3D panels are loaded through the model code, and never get a chance to register themselves as the "current_panel" object in globals. Is there an invisible 2D panel loaded from somewhere else? FWIW, I still haven't been able to duplicate the rogue mouse click problem.
- Julian
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
