Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!kth!osiris!pd@sics.se
From: pd@sics.se (Per Danielsson)
Newsgroups: comp.sys.next
Subject: Re: Next and the competition
Message-ID: <2397@osiris.sics.se>
Date: 28 Dec 88 08:59:52 GMT
References: <29866@tut.cis.ohio-state.edu> <5567@cbmvax.UUCP> <361@internal.Apple.COM>
Sender: pd@osiris.sics.se
Reply-To: pd@sics.se (Per Danielsson)
Organization: Swedish Institute of Computer Science
Lines: 21
In-reply-to: casseres@Apple.COM (David Casseres)

In article <361@internal.Apple.COM>, casseres@Apple (David Casseres) writes:
>Gee, just what are "all" aspects of a window?  Should the OS also do the
>selection and highlighting of objects in the window when the user clicks
>the mouse?  Maybe it should guess what the application wants to draw in
>the window, and do the drawing?  After all, refreshing a window does in-
>volve drawing its content.  Or maybe you mean that refreshing should only
>be done by saving the bits of the window's current image, then restoring
>them when a refresh is needed.  Too bad if the content of the window wanted
>to change before the refresh.

Moving a window should not require redrawing the contents. From the
applications point of view it shouldn't matter that the user moves the
window. The application shouldn't even know about it.
I don't see why this is a problem at all. These kind of problems with
window systems were solved years ago.

PD
Per Danielsson		UUCP: pd@sics.se (or ...!enea!sics!pd)
Swedish Institute of Computer Science
PO Box 1263, S-164 28 KISTA, SWEDEN
"No wife, no horse, no moustache."