(this is a topic about xlib events)
who can teach me how to deal this?
first, hold up a message from the event queue;
second, add our code(or not);
third, call the default message process function(or put back the event to the message pump).

this may work like the win32's function: DefWindowProc().

Example(a xlib code):
{
....
XSelectInput(dpy, win, ResizeRedirectMask) ; //hold up ResizeRequest mask
while(1) {
...
switch(e.type)
{
case ResizeRequest: //process it here,
this is my problem //we want back to the pump, let the pump do the default process
break;
}
}
}
hay, who can do this for me? thanks!

perhaps im misunderstanding your bad english, but it sounds like you want to toss a event back into the queue?

There should be no need to do this, why cant you handle the event right there. If you cant handle it, then you shouldent have requested it. Also, the only way i know to place a even onto the queue is to generate a fake event, and send it to yourself, but then you would only have to deal with it again, and it would be a nasty memory leak in your program as the queue fills with fake events your code doesnt properly handle.

Another way to read what you have, is that you are expecting multiple programs to be gathering events for the same window. I dont recall this ever being possible either, nore should it be necessary.

Odds are, you are trying to place a event that was sent to you back onto the queue (or anywhere, really), you have a bad architecture designed for your program.

maybe XtAddEventHandler

http://www.xfree86.org/current/XtAddEventHandler.3.html

what exactly are you trying to do?