Xref: utzoo comp.windows.x.motif:984 comp.windows.x:28590 Path: utzoo!attcan!uunet!ibism!ibism.UUCP!lcp From: lcp@ibism.UUCP (Larry Poleshuck) Newsgroups: comp.windows.x.motif,comp.windows.x Subject: Re: Question about XtAddInput Message-ID: <12050@ibism.uucp> Date: 22 Oct 90 20:39:07 GMT References: Sender: news@ibism.uucp Reply-To: ibism!lcp Organization: Citibank IBISM Lines: 32 In article , gjf00@duts.ccc.amdahl.com (Gordon Freedman) writes: > > I am running Motif (from Quest windows) with X11-R4.0 on a Solbourne 4-500 > (essentially a Sparc system) running Sunos. I'm having a problem with > XtAddInput. I'm using XtAddInput as described in "X Toolkit Intrinsics > Programming Manual (Volume 4)" (O'Reilly and Assoc) section 8.3 (File, > Pipe, and Socket Input). > > The problem I am having is that my input handler does not get called unless > other ("normal") X events are also available. A footnote on page 224 says > this behavior is a bug in R3, but is *not* a bug in R4. I am compiling with > a make file using the following: > ... > -- > Gordon Freedman: gjf00@duts.ccc.amdahl.com > Disclaimer: My opinions! Not my employers! I use an XtAddInput (with the read mask only) in a TeleUSE MOTIF application. I have no problem getting my input routine executed even though there are no X events in the queue. This is X11R3 with the appropriate patches for Motif 1.0.3 as supplied by TeleSoft. Larry Poleshuck Citibank 111 Wall Street New York, NY 10043 Phone: 212-657-7709 Fax: 212-657-0068 E-Mail: uunet!ibism!lcp