I've seen this problem also. I believe it occurs because wmii does not
send a synthetic ConfigureNotify event in some cases in response to
ConfigureRequest events, as the ICCCM requires; as a result, I believe
some programs end up waiting for a little while for the synthetic
ConfigureNotify to come. The fix is to make wmii properly send
synthetic ConfigureNotify events. I have written a patch to do this
(and which fixed the problem for me) for a particular snapshot of wmii 4
(which I also posted to this list previously):
http://www.andrew.cmu.edu/user/jmaitins/wmii-20060705-improvements.diff
This patch includes a bunch of stuff, but you can try to extract the
relevant portion. Alternatively, you could just write your own patch
which does things a bit more properly than mine.
-- Jeremy Maitin-ShepardReceived on Thu Oct 19 2006 - 00:53:10 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:16:09 UTC