|
XCIN Mail-list
|
| Indexed By Date: [Previous] [Next] | Indexed By Thread: [Previous] [Next] |
| Subject: | Re: Endless events |
| From: | Yung-Ching Hsiao <hsiaoy@ee.eng.ohio-state.edu> |
| Date: | Sat, 3 Jul 1999 03:16:05 -0400 |
| To: | xcin@linux.org.tw |
| Mail-Followup-To: | xcin@linux.org.tw |
| Reply-To: | xcin@linux.org.tw |
On Jul 03(Sat) 09:40AM, hashao wrote:
> Okey, I come across it now. It seems like the xcin server received
> some kind of ClientMessage (I assume that the xcin selected the event).
> Then the xcin filtered the event and sent out some composed char. In
> return, it got another ClientMessage, and it filtered, composed and the
> thing goes on and on and on. Maybe some race condition happened.
This seems like some kind of bad interaction between the XFilterEvent
machanism and the Shade (Shrink to Title bar) feature of the window manager.
Maybe you should print out the type of XClientMessage to check what has
been filtered:
XNextEvent(&ev)
if (XFilterEvent(&ev)==Filtered) {
if (ev.any.type==ClientMessage)
dump_clientmessage(&ev);
continue;
}
| Indexed By Date | Previous: |
Re: Endless events From: Tung-Han Hsieh <thhsieh@linux.org.tw> |
|---|---|---|
| Next: |
About ETen keyboard (bims) From: Tung-Han Hsieh <thhsieh@linux.org.tw> |
|
| Indexed By Thread | Previous: |
Re: Endless events From: Tung-Han Hsieh <thhsieh@linux.org.tw> |
| Next: |
Re: Endless events From: Tung-Han Hsieh <thhsieh@linux.org.tw> |