| Re: XLoadCT in a procedure ????? [message #5289 is a reply to message #5288] |
Fri, 17 November 1995 00:00  |
rivers
Messages: 228
Registered: March 1991
|
Senior Member |
|
|
In article <48esa3$8a3@mirv.unsw.edu.au>, jgm@nntp.unsw.EDU.AU (Julian Marshall) writes:
> Hi.
> I have a slight problem with Xloadct. It does not behave well
> when used inside a case statement in a procedure. When Xloadct
> is in a procedure, the pro naturally waits for xloadct to be
> finished before continuing, but when I use Xloadct within a
> case statement, the event handler does not seem to wait for
> the Xloadct pro to finish.
I don't believe that your statement "When Xloadct is in a procedure, the pro
naturally waits for xloadct to be finished before continuing" is correct.
XloadXT creates its widgets and then just registers itself with Xmanager, and
immediately returns. In many applications this is the way one wants it to work.
Pressing the "Change Color" button on an application pops up XloadCT, which
then stays around, allowing the use to change colors whenver they want, i.e.
they don't have to press "Change Color" again. There is probably a way to get
the behavior you want, i.e. the program waits until the user exits XloadCT,
perhaps by making a "modal widget" which calls XloadCT.
____________________________________________________________
Mark Rivers (312) 702-2279 (office)
CARS (312) 702-9951 (secretary)
Univ. of Chicago (312) 702-5454 (FAX)
5640 S. Ellis Ave. (708) 922-0499 (home)
Chicago, IL 60637 rivers@cars3.uchicago.edu (Internet)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
