Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!eru!hagbard!sunic!bmc.uu.se!heap
From: heap@bmc.uu.se
Newsgroups: comp.windows.x.motif
Subject: Re: Problem using the WorkingDialog
Message-ID: <1990Oct14.194243.3544@bmc.uu.se>
Date: 14 Oct 90 18:42:43 GMT
References: <9010101547.AA05309@bellcore.bellcore.com>
Distribution: inet
Organization: Biomedical Center, University of Uppsala, Sweden
Lines: 22

In article <9010101547.AA05309@bellcore.bellcore.com>, aw@KITCHEN.BAE.BELLCORE.COM (Andrew Wason, aw@cellar.bae.bellcore.com) writes:
> 
> Could you use XmUpdateDisplay(workdialog) to make sure
> the dialog box is completely drawn before doing your long computation.
> I haven't tried this, so I don't know if it would work or not,
> but the manual suggests that this is what this function is for.
> 
> Andrew
> 

I tried this call, but it gives me the same result as my original
code did (that is, the window of the workingdialog is displayed, but not its
contents). Am I supposed to use XmUpdateDisplay on every little subwidget in
the dialog (or should I have used something else than the widget returned from
XmCreateWorkingDialog as the parameter to XmUpdateDisplay) ??

----------------------------------------------------------------------
Per Bengtsson, Dept. of Scientific Computing, Univ. of Uppsala, Sweden

Internet:       heap@tdb.uu.se
Sunet/Decnet:   tdb::heap
----------------------------------------------------------------------