[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can we go GTK-only?

From: Eli Zaretskii
Subject: Re: Can we go GTK-only?
Date: Mon, 31 Oct 2016 05:37:57 +0200

> From: Stefan Monnier <address@hidden>
> Date: Sun, 30 Oct 2016 19:57:31 -0400
> Cc: Ken Raeburn <address@hidden>, address@hidden
> > The key insight there is that we shouldn't have redisplay *lock* the display
> > matrix and render it.  The lisp universe should send a *copy* of the matrix
> > set, then go about its business.
> Good, point we can decouple the two a bit more this way.  Actually, we
> already have this copy since we have 2 sets of matrices.  So we just
> need to say that the "current matrix" belongs to the GUI thread/process,
> while the "desired matrix" belongs to the redisplay.  And the "send
> a copy" is done by comparing the two, so only the part that changed is
> sent (and so the GUI thread gets to know which part needs to be redrawn).
> Of course, comparing the two sets of matrices requires access to both,

What's more, some redisplay optimizations use the current matrices
without constructing the desired ones.

But since the matrices are not exposed to Lisp, I don't understand why
you think there's any problem to be solved here.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]