> X11's own "KeyRelease" events seem to behave similarly; > in my tests with the pure X11 code below, when X11 sends > a KeyRelease event for the capslock key, the "event.xkey.state" > shows accurate info when capslock is ENABLED, but INACCURATE INFO > when capslock is disabled. > > You have to hit some other key to get the accurate state of > capslock after lock release.
Yes - though with Howard's example I find (on a F17 VM, not a "real" computer) that (as Howard said) quite often (not always!) just wiggling the mouse about in the window gets the state to update correctly... (Or, hitting the space bar always seems to!) So, something in the state is getting updated by other events, and perhaps not just the X11 KeyRelease ones? Or I'm missing the point again... Selex ES Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
