X-event problem

New Message Reply Date view Thread view Subject view Author view

Kapil R. Dandekar (dandekar++at++itd.nrl.navy.mil)
Wed, 24 Jul 1996 14:13:58 -0400 (EDT)


Hi everyone,

   I was wondering if any of you could answer (or indicate references for)
a question that I have concerning the use of X-Events with multi-process
Performer applications. Basically, I need to be able to use the
XSendEvent routine to send a XClientMessageEvent from one process
to another. If I use this XSendEvent in a single process Performer
application, everything works fine: the sent event is received by
the X-event handler. However, if I use a multi-process program, the
X-event handler in the main app process apparently does not get
any of the sent ClientMessage events.

   The format of the XSendEvent command is:
XSendEvent(display, windowID, propagate, event_mask, Xevent_send)

   Knowing that ClientMessage events do not require a mask (event_mask = 0)
the XSendEvent man page says "the event is sent to the client that created the
destination window". Even though the X-window is mapped in the main app
process which also contains the X-event handler, the event is not sent
to the X-event handler... it just disappears. However, to make it a little
more strange, event types that do require a mask can be sent without
a problem in either single process or multiprocess program using the
XSendEvent command. Individual windows, even when configured in the
draw process, are perfectly capable of having their buttonpress, keypress,
etc. events sent to the X-event handler in the main app process (which, BTW,
is the process in which the XMapWindow routine is used on the window).

   I'd greatly appreciate any help that you all can offer concerning this
problem. Thank you very much!

Regards,
Kapil

-- 
Kapil R. Dandekar
dandekar++at++itd.nrl.navy.mil		
Interface Design and Evaluation - Naval Research Laboratory 
(202)767-5613
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:13 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.