Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: I need Help with the A3000! Message-ID: <6121@sugar.hackercorp.com> Date: 1 Aug 90 22:05:00 GMT References: <6071@sugar.hackercorp.com> <13386@cbmvax.commodore.com> <6091@sugar.hackercorp.com> <1990Jul25.224140.24184@cbnewsm.att.com> <13456@cbmvax.commodore.com> <13489@cbmvax.commodore.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Distribution: usa Organization: Sugar Land Unix - Houston Lines: 23 In article <13489@cbmvax.commodore.com> dale@cbmvax (Dale Luck - Amiga) writes: > Most X implementations do support SMARTREFRESH like capabilities. ^^^^ vvvvvvvvvvvvvvvvvv ^^^^ <--- important words > MIT only says you can't depend on it being there if you want your > product to be completely transportable to all other servers. Or even reliably on a given server, since it is legal for any server to ignore the backing-store hint if it starts getting low on RAM. SO, your program has to redundantly include all the simple-refresh-style code to handle expose events anyway. And that is really dumb: a window should be able to be treated as a virtual screen. Expecting a program to handle its own expose events is like expecting it to handle its own page faults. It's a nice option to have available, but it sure adds a lot of un-needed complexity. Expecting a program to handle its own menus is like expecting it to handle erase and kill. Important to have available, but do you want to put all that code in "cat"? X requires this as well. -- Peter da Silva. `-_-' .