[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3 button mouse (was: Re: [MiNT] X magic)
- To: Kristoffer Lawson <setok@fishpool.com>
- Subject: Re: 3 button mouse (was: Re: [MiNT] X magic)
- From: Michael Schwingen <rincewind@tubul.dascon.de>
- Date: Tue, 8 Dec 1998 20:26:28 +0100
- Cc: MiNT mailing list <mint@fishpool.com>
- In-reply-to: <Pine.LNX.3.96.981208193950.3282L-100000@gfanrend.fishpool.com>; from Kristoffer Lawson on Tue, Dec 08, 1998 at 07:42:02PM +0200
- References: <Pine.LNX.4.05.9812081725270.78-100000@bluto> <Pine.LNX.3.96.981208193950.3282L-100000@gfanrend.fishpool.com>
- Sender: owner-mint@fishpool.com
On Tue, Dec 08, 1998 at 07:42:02PM +0200, Kristoffer Lawson wrote:
> Are you sure this is true? AFAIK X applications redraw the window
> themselves, but X is capable of caching to at least some extent. This was
Correct. You get redraw messages just like in AES. The X server may
implement backing store (to buffer invisible window contents and do a local
redraw when they are exposed), but this does not seem to be used very often.
The X protocol and Xlib are designed so that the events are mostly
asynchronous: most query functions are handled by the Xlib from locally (on
the X application side) cached values, and drawing requests are sent to the
server without waiting for a response, while the server sends the required
events (mouse, redraw etc.).
This also means that you can get an error (bad drawable, invalid parameter
or such) after a lot of other commands are already processed by the X
server.
cu
Michael
--
Michael Schwingen, Ahornstrasse 36, 52074 Aachen