> (Maybe I shouldn't say broken; it's pejorative. Just "differently
> abled"...)

Yes, that sounds better :).  In fact one might argue the documented behavior is 
broken and the current "differently abled" behavior is preferable.

XGrabPointer(...) and XGrabKeyboard(...) are the underlying library routines 
FLTK calls to do the deed.  They both return obscure, but meaningful values, 
which FLTK ignores.   I imagine Xorg may well be declining FLTK's request and 
trying to tell FLTK about it.

Unlike window positioning and resizing operations, which application authors 
are repeatedly warned "are only requests", XGrabPointer/XGrabKeyboard 
documentation seems to imply they will be honored unless something drastic goes 
wrong, like "your machine has just caught fire!"

The upshot is, that I'm not sure Stan's problem is fixable.  If the server 
declines to obey the request, FLTK provides no mechanism to inform your 
application of the failure, and there's not a lot your application could do 
about it anyway.

Jim
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to