Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!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: <385.2833079e@beach.gal.utexas.edu>
Date: 17 May 91 04:28:46 GMT
References: <378.2830d367@beach.gal.utexas.edu> <1228@cbmger.UUCP>
Lines: 27


 
>>2) Is there a way to safely (or reasonably safely) change the contents of
>>screens/windows opened by other processes?  Using public screens would be
>>lovely, unfortunately the screens I want to write to are created by programs
>>that do not use public screens, like my term program.
> 
> Why on earth do you want to stomp someone other's screen? This is
> normally considered a no-no. But you mentioned public screens: Yes,
> these are part of the news in OS 2.0 and are intended exactly to
> allow this. 

	Public screens are a marvelous idea and I am glad that Commodore 
decided to implement them. 

	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. 

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