home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!psinntp!svc!news
- From: moose@svcdudes.com
- Subject: Re: Destroying Zones
- Message-ID: <1992Jul27.164851.28178@svcdudes.com>
- Sender: news@svcdudes.com
- Reply-To: moose@svcdudes.com
- Organization: Software Ventures, Inc.
- References: <1992Jul27.010436.1749@kakwa.ucs.ualberta.ca>
- Distribution: na
- Date: Mon, 27 Jul 92 16:48:51 GMT
- Lines: 27
-
- In article <1992Jul27.010436.1749@kakwa.ucs.ualberta.ca>
- gary@niagara.ucs.ualberta.ca (Gary Ritchie) writes:
- > I'm loading a nib file into its own zone, so that I can later destroy the
- > zone and make everything go away. I'm having a problem because the nib
- > file contains Windows, and the program has a segmentation fault shortly
- > after the zone is destroyed.
- >
- > I remember glancing at an article in the spring NeXTworld magazine which
- > discussed how to deal with freeing zones which contain Windows, but I
- > don't have access to that particular issue anymore.
- >
- > Could someone give me a quick summary on the steps necessary?
-
- Grab the entire window list and iterate through it. You can find all the
- windows you want by doing a [[windowList objectAt:count] zone] == ZoneToDie.
-
- Something to note, though, NeXT puts icons and sounds in whatever zone was
- active when the tiff was loaded. But future loadings will not reload the tiff,
- but point to the already existing tiff. Therefore, if you kill a zone, you
- will kill tiffs that other zones point into.
-
-
- --
- Michael Rutman | moose@svcdudes.com
- Cubist | makes me a NeXT programmer
- Software Ventures | maker of MicroPhone II
- #include <std.disclaimer>
-