On Fri, 17 Dec 2004 00:51:14 -0600 (CST) [EMAIL PROTECTED] (Joel L. Breazeale)
(Bbabbled:
(B
(B> Please pardon what may be a very nieve question from a newbie! Please
(B> also pardon me if this question is off topic? Otherwise, my question
(B> has a slim chance of exposing a problem in XFree86 (I highly doubt it,
(B> but we'll see).
(B>
(B> On my XSetInputFocus() man page it says, "XSetInputFocus() can generate
(B> BadMatch, BadValue, and BadWindow errors."
(B>
(B> In looking at the source code for XFree86 4.2.1, I see XSetInputFocus()
(B> in lib/X11/SetIFocus.c always returns 1. In looking at the Xserver source
(B> code in programs/Xserver/dix/events.c, I see ProcSetInputFocus() calls
(B> SetInputFocus() which returns BadMatch, BadValue, and BadWindow (or Success).
(B> [This agrees nicely with the man page.]
(B>
(B> When my application calls XSetInputFocus() the return value is always 1
(B> (BadRequest). BadRequest is not one of the values returned by
(B> SetInputFocus(). The value 1 is the value returned by XSetInputFocus().
(B>
(B> So... When I call XSetInputFocus() and get a return value of 1 what
(B> does this mean? If I am supposed to get either BadMatch, BadValue,
(B> BadWindow, or Success (my preference) then where are those set? Perhaps
(B> the errors are only raised via an error handler?
(B
(Bit will always return 1... BUT... you may LATER get an error from x (set your x
(Berror handler) and THIS will then tell you your set focus request had a badmatch
(Betc. it happens some time later on. not right away.
(B
(B--
(B------------- Codito, ergo sum - "I code, therefore I am" --------------
(BThe Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
$BMg9%B?(B [EMAIL PROTECTED]
(BTokyo, Japan ($BEl5~(B $BF|K\(B)
(B_______________________________________________
(BDevel mailing list
([EMAIL PROTECTED]
(Bhttp://XFree86.Org/mailman/listinfo/devel
