Path: utzoo!attcan!uunet!mcsun!ukc!harrier.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (Richard Hesketh)
Newsgroups: comp.windows.x
Subject: Re: X routines running on child processes
Message-ID: <5200@harrier.ukc.ac.uk>
Date: 29 Jul 90 11:47:31 GMT
References: <9007281621.AA07911@mn.ecn.purdue.edu>
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 14
Summary:
Expires:
Sender:
Followup-To:

In article <9007281621.AA07911@mn.ecn.purdue.edu> tongz@MN.ECN.PURDUE.EDU (Tong Zheng) writes:

> ...
>to update the screen, e.g, change the XtNlabel for a label widget.
>The problem is that all changes are not seen on the window
>until I move the cursor to the window.

I've seen this sort of problem before when using multiple event sources.
Try using XFlush() after you make the necessary screen changes.
This flushes any buffered requests off to the server which would then
generate any events (such as the expose caused by the set values) which
you will then be able to process.  I suspect this flushing is being done
for you by the window manager setting the input focus when you move
the cursor back in the window; well thats a guess anyway.