I ran into this problem very recently too on a Win32 system. The solution I had to adopt was checking the modifier keys using the Win32 API's GetKeyState function when processing a key that's affected by modifiers.
I agree that it probably shouldn't be OSG's responsibility to account for this problem. However, part of the problem stems from OSG attempting to support, given a false sense of security. On the Windows side, we could explicitly poll a modifier key's state before sending an event off to the EventQueue, without relying on KEYUP/KEYDOWN synchronization. However, doing something like that would cause inconsistencies between the platforms, and I don't know if the X11 has a counterpart. Chase > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:osg-users- > [EMAIL PROTECTED] On Behalf Of Melchior FRANZ > Sent: Tuesday, February 05, 2008 1:35 PM > To: osg-users@lists.openscenegraph.org > Subject: Re: [osg-users] X11 keyboard bug (+ ugly fix) > > * Jean-Sébastien Guay -- Tuesday 05 February 2008: > > For reference, the same thing happens on Windows, > > Oh, didn't know that. > > > > > Not sure if OSG should try to work around it or not... > > Well, but it's annoying as hell, and my computer is not > supposed to annoy me. :-) > > And again: I never saw that in FlightGear when linked with > glut or sdl. (We still support all three, but will probably > go for osgviewer only.) > > m. > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
