Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!canon!laukee
From: laukee@canon.co.uk (David Lau-Kee)
Newsgroups: comp.windows.news
Subject: Re: Hunh?
Message-ID: <1990Jul19.153846.1586@canon.co.uk>
Date: 19 Jul 90 15:38:46 GMT
References: <9007161732.AA01251@>
Organization: Canon Research Europe, Guildford, UK
Lines: 38

bice@hbo.UUCP (Brent A. Bice) writes:

...
>entry I want to have a function that will spawn a completely independent
>window.  When the main window gets Zap'd, it should go away, but not kill
>the window/s that it spawned.  I have a piece of code that does this, but
>the main window won't die until all of the other window/s that it spawned
>also are zapped.   Howcomeforwhy?   Am I missin' somethin' here?

Yeah, I found this too.  I never did get round to understanding what was
happening, but I worked around using a separate file and runprogram (which
is actually closer to the semantics I want anyway).

Something like:

/buttoncallback
{
	/graphic exch send /thing exch send
	{
		(Images) { /spawnimagebrowser self send }
		(Book) { /spawnbook self send }
		(Viewer) { /spawnviewer self send }
	...
	} case
} def

/spawnimagebrowser
{
	(/usr/vpl/demo/imagebr.ps) runprogram
} def

-------------
David Lau-Kee
Canon Research Centre Europe,
17/20 Frederick Sanger Rd, Surrey Research Park, Guildford, Surrey, GU25YD, UK.
NRS: laukee@uk.co.canon, INET: laukee%canon@nsfnet-relay.ac.uk
UUCP: laukee@canon.uucp, PATH: ..!mcsun!ukc!uos-ee!canon!laukee
Tel: +44 (0) 483 574325 Fax: +44 (0) 483 574360