Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!beach!mrimages
From: mrimages@beach.gal.utexas.edu
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Kill and Getting Killed, heh.
Message-ID: <392.2833d785@beach.gal.utexas.edu>
Date: 17 May 91 19:15:49 GMT
References: <378.2830d367@beach.gal.utexas.edu> <1228@cbmger.UUCP> <385.2833079e@beach.gal.utexas.edu> <1991May17.193919.24599@wehi.dn.mu.oz>
Lines: 26

In article <1991May17.193919.24599@wehi.dn.mu.oz>, baxter_a@wehi.dn.mu.oz 
writes:
> In article <385.2833079e@beach.gal.utexas.edu>, mrimages@beach.gal.utexas.edu
> writes:
>> 	Still, have you ever wanted to print a small message or perhaps a 
>> clock in the most remote of places of another application's screen? OK, maybe
>> you haven't, but I have. Anyway, here's what I do, and it works on my screen, 
>> but then the machine has problems running new tasks or opening new screens or
>> windows. In my new program I have a screen structure assigned the address to 
>> the screen opened by the other application. (basically by locking the
>> IntuitionBase and making my_screen=IntuitionBase->FirstScreen->NextScreen, 
>> then unlocking the base again.) Then I write on the screen like I would any
>> other screen.  Why would this present a problem? Seems pretty harmless to me,
>> especially because I am not changing any Base values. 
> 
> And then the screen closes.
> 
> And then you write to it.

	Well, actually, this is not possible, because if
IntuitionBase->FirstScreen->NextScreen==NULL the program exits without writing
anything anywhere.  Each time I am about to write I make SURE the screen is
still there and still has the same address, using basically the same technique
as above every time I want to update my message.

R. Luebbert = mrimages@beach.gal.utexas.edu (U.T. Medical Branch Galveston)