Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!beach!mrimages
From: mrimages@beach.gal.utexas.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: RKMs and Screens
Message-ID: <446.284e88e5@beach.gal.utexas.edu>
Date: 7 Jun 91 01:11:33 GMT
References: <426.284909a9@beach.gal.utexas.edu> <22176@cbmvax.commodore.com>
Lines: 20

In article <22176@cbmvax.commodore.com>, spence@cbmvax.commodore.com (Spencer Shanson) writes:
> In article <426.284909a9@beach.gal.utexas.edu> mrimages@beach.gal.utexas.edu writes:
>>
>>	Would anything strange be expected to happen if I change the BitMap of
>>a screen opened by another program? If so, what? and how would I get around
>>the problem?
>>
> Generally, if you don't own a resource, keep well away from it. As Peter would
> tell you, it's 'impolite' to start modifying another screen's or window's
> appearance, so there should be no reason for you to modify another screen's BitMap.
> 
> Furthermore, you cannot know what the application is doing with it's BitMap. For
> all you know, it may be doublebuffering the BitMap structure in its screen, so
> you would only get one BitMap, and you wouldn't know that there is another.
> 

What if you know these things in advance?


R. Luebbert