Curtis L. Olson wrote: > Andy, very cool, almost works reliably. Definitely a huge addition to > the 3d panels, great work! > > I did notice on rare occasion some areas were getting mismapped. > I.e. I couldn't click on the wing leveler, but I could click the other > autopilot buttons. Another time I was trying to switch the DME > between nav1 and nav2 and my right engine died ... looks like the > magneto switch mistakenly grabbed the click. But most of the time the > stuff works great!
Uh... dunno. Haven't seen this behavior yet. How rare? Maybe we should put in some debug logging so we can see the panel coordinates that got generated from the input screen coordinates. Were you in the process of panning or switching the view? The code works by storing the "last" matrix environment seen. If there was a frame or two of latency between the glutSwapBuffers() and the mouse event delivery, then I guess something like this could happen. Then again, it's awfully hard to imagine a human being hitting a mouse target within 1/20 of a second after a view change... Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
