On 11-Mar-96 18:47:46 chuck_hines_at_VNET.IBM.COM wrote:
>>>>>>> "Grant" == Grant McDorman <grant_at_isgtec.com> writes:
>
>Grant> On 11-Mar-96, Mark Borges wrote:
>>> X Error of failed request: BadMatch (invalid parameter attributes)
>>> Major opcode of failed request: 42 (X_SetInputFocus)
>>> Serial number of failed request: 41231
>>> Current serial number in output stream: 41266
>
>Grant> This is a timing problem in FvwmPager. I posted a patch some
>Grant> time ago, but either it didn't make it to the list or it has
>Grant> not been applied.
>
>I have that patch still, but it frightened me somewhat, so I haven't
>played with it yet. It's the sleep that bothers me, actually. I
>understand the sync, but I want to know why the sleep is needed. I'm
>wondering if there isn't a more correct fix (if not, of course I'll
>use yours). I'll look into it when I get a chance.
It seems to me that there is some period of time between sending the
XReparentWindow (a few lines above) and the server actually accomplishing
the reparenting. If the FvwmPager tries to set the focus before the
reparenting is complete, the BadMatch error happens.
Incidentally, I reduced the delay from 50,000 to 5,000 (microsec) when
installing 2.0.41 and it still seems to work fine. I agree, though, that it
would be nice to have something other than a delay. About the only thing I
can think of, though, is to wait for an event, such as ReparentNotify, which
would be a pain (and would also, presumably, have to time out to prevent the
pager from locking up if something goes wrong).
Grant McDorman <grant_at_isgtec.com>
ISG Technologies, Inc.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Mar 11 1996 - 13:03:33 GMT