home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!spool.mu.edu!olivea!charnel!durian28
- From: durian28@ecst.csuchico.edu (dl)
- Newsgroups: comp.windows.x
- Subject: Does XtCloseDisplay() destroys windows?
- Message-ID: <1iin9eINN2lr@charnel.ecst.csuchico.edu>
- Date: 8 Jan 93 02:01:18 GMT
- Organization: California State University, Chico
- Lines: 31
- NNTP-Posting-Host: bolger.ecst.csuchico.edu
-
-
- I am writing a single application context program with multiple displays
- in hpux 8.0/Motif1.1 environment.
-
- I seemed to have problems with XtCloseDisplay().
-
- Scenerio:
- 1. Created a display with XtOpenDisplay() and used XtAppCreateShell(),
- XtCreatePopupShell() to create a toplevel widget as the parent
- for other windows in that display.
- 2. Then, I remove the display with XtCloseDisplay().
- 3. When I reopens the same display (step #1) and tried to create widgets,
- I get the following warning:
- "Warning: Try to change value of a registered window."
- and then core dumps.
-
- Temporary solution:
- - Instead of XtCloseDisplay(), I use XtDestroyWidget() on the toplevel widget.
- Now, the program runs perfectly, I think. Will there be any future problem
- by not closing those displays with XtCloseDisplay()?
-
- Main questions:
- 1. Will there be any future problem by not closing the displays with
- XtCloseDisplay()?
- 1. Does XtCloseDisplay() destroys windows?
- 2. If it does, what's my mistake?
-
-
- THANKS IN ADVANCE.
-
- -dennis-
-