Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Re: overlay canvases
Message-ID: <870605081110.1.RWS@KILLINGTON.LCS.MIT.EDU>
Date: Fri, 5-Jun-87 08:11:00 EDT
Article-I.D.: KILLINGT.870605081110.1.RWS
Posted: Fri Jun  5 08:11:00 1987
Date-Received: Tue, 9-Jun-87 06:50:52 EDT
References: <8706041752.AA25242@ramoth.sgi.com>
Sender: usenet@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 16


    Again these are weaknesses in the implementation not in the model.

I guess I don't see that much of a distinction.  Unless you somehow
think the implementation will get wonderfully better (without the
hardware changing), the fact seems to remain that a) an application
had better not depend on overlays for much and b) an application
doesn't seem to have any facilities for finding out what properties
overlays really have.

    My preferred paint palette is the whole screen anyway.  I wouldn't use
    a menu.  I'd just let you pick any color on the screen.
	
User-interface religion as a justification for not providing mechanism ...
Not to belabor this discussion, but somehow I doubt your screen starts off
with 2^24 colors already on it from which to "pick".