Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!bionet!uwm.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!munnari.oz.au!ariel!ucsvc.ucs.unimelb.edu.au!wehi.dn.mu.oz!baxter_a
From: baxter_a@wehi.dn.mu.oz
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Kill and Getting Killed, heh.
Message-ID: <1991May17.193919.24599@wehi.dn.mu.oz>
Date: 17 May 91 19:39:19 GMT
References: <378.2830d367@beach.gal.utexas.edu> <1228@cbmger.UUCP> <385.2833079e@beach.gal.utexas.edu>
Organization: Walter & Eliza Hall Institute
Lines: 17

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.

Regards Alan