home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!INTERNET!dont-send-mail-to-path-lines
- From: mahan@TGV.COM (Patrick L. Mahan)
- Newsgroups: comp.windows.x
- Subject: RE: how to implement slow calback routines ?
- Message-ID: <920827104953.21000150@TGV.COM>
- Date: 27 Aug 92 17:49:53 GMT
- Sender: daemon@athena.mit.edu (Mr Background)
- Organization: The Internet
- Lines: 24
-
- #
- #My problem is the following :
- #
- #In several applications we add a callback routine to a pushbutton, let us say
- #that foo is this callback routine.
- #In foo, we have to access large numbers of pieces of equipment;this operation
- #may take up to 30 seconds. Therefore, we pop up an a XmMessageBox telling the
- #user that the task in currently running.
- #The problem is that after the creation of the messagebox we do not return to
- #the XtMainLoop() and the messagebox is not managed on the screen, even if we
- #call XFlush().
- #
-
- You need to register a Work Proc inside of the button callback to acutally
- do the work for you. This will allow 1) the message box to actually show
- up and 2) let you complete your task.
-
- Patrick L. Mahan
-
- --- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------
-
- Waking a person unnecessarily should not be considered - Lazarus Long
- a capital crime. For a first offense, that is From the Notebooks of
- Lazarus Long
-