home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!utcsri!skule.ecf!torn!spool.mu.edu!agate!stanford.edu!sun-barr!sh.wide!wnoc-tyo-news!scslwide!wsgw!wsservra!daemon
- From: devuns@alsys.fr (Olivier Devuns)
- Newsgroups: fj.mail-lists.x-window
- Subject: Modality, Motif & the Intrinsics
- Message-ID: <1993Jan26.145452.19073@sm.sony.co.jp>
- Date: 26 Jan 93 14:54:52 GMT
- Sender: daemon@sm.sony.co.jp (The devil himself)
- Distribution: fj
- Organization: Workstation Div., Supermicro Systems Group, Sony Corporation
- Lines: 35
- Approved: michael@sm.sony.co.jp
-
- Date: Tue, 26 Jan 93 13:59:21 +0100
- Message-Id: <9301261259.AA01789@venus.alsys_sa>
-
- Hi xperts,
-
- Thanks to jcb@hal.com (Joe Beall) who answered my previous modality
- question. I think I finally found the answer in the Intrinsics. The
- problem was to allow access to a permanent help in its own topLevelShell
- while the rest of the application is blocked on a modal dialog, such as
- a MOTIF MessageDialog instance.
-
- The solution I found is to add the help window to the modal cascade
- by just calling :
- XtAddGrab (HelpWidget, False, False);
- in the modal dialog's help callback; this allows input to be sent to
- the help window and to the modal dialog as well.
-
- When the modal is dismissed, don't forget to remove the grab if it
- has been added :
- if (grab_added)
- XtRemoveGrab (HelpWidget);
-
- and you'll want to do that usually in the modal dialog's unmap callback.
-
- Maybe that solution was known-to-everybody-for-years, but since nobody
- but Joe answered, I guess broadcasting it again can be useful to others...
-
- -----------------------------------------------------------------------
- Olivier Devuns -- Ada Tools Development Engineer
- ALSYS -- 29 Ave. LR Duchesne, 78170 La Celle St Cloud - FRANCE
-
- Email : devuns@alsys.fr Voice : (1)30781727
-
- "Views expressed are my own."
- -----------------------------------------------------------------------
-