[Top][All Lists]

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

Re: Redisplay problems?

From: Stefan Monnier
Subject: Re: Redisplay problems?
Date: Thu, 20 Mar 2014 16:55:52 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

>> So "garbaged" means that we should not try to only redraw the parts that
>> have changed.
> When redisplay finds that a frame is "garbaged", it marks all of its
> glyph matrix rows "disabled".  This will force their complete
> redrawing, as described above.

Right, but that's not how "garbaged" is described (e.g. in the comment
before it: "True if this frame should be redrawn"), hence the fuzzyness.

The way I see it described, "garbaged" means that the display is not in
sync with the matrices any more, but not that the matrices need to
be recomputed.

But the implementation you describe here implies that "garbaged" will
end up recomputing all the matrices.

And in turn I suspect some of the code takes advantage of the knowledge
of how "garbaged" is implemented: it sets "garbaged" to cause the
matrices to be recomputed (and the frame redrawn redrawn).

> I don't think I understand what you meant to say here.  But if you
> were talking about what to do about a frame that was deiconified, I
> think you need to call expose_frame, and arrange for the exposed
> rectangle to cover the entire frame.  That should do what you want, no
> more, no less.

Doesn't the windowing-system do that already for us?


reply via email to

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