GNU bug report logs - #30699
26.0.91; buffer contents flicker on macOS frames when frames are resized

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Third <alan <at> idiocy.org>
Cc: 30699 <at> debbugs.gnu.org, aaronjensen <at> gmail.com
Subject: bug#30699: 26.0.91; buffer contents flicker on macOS frames when frames are resized
Date: Wed, 07 Mar 2018 19:26:01 +0200

> Date: Tue, 6 Mar 2018 22:55:02 +0000
> From: Alan Third <alan <at> idiocy.org>
> Cc: 30699 <at> debbugs.gnu.org, aaronjensen <at> gmail.com
> 
> In theory if you call NSDisableScreenUpdates before the blanking of
> the frame, then call NSEnableScreenUpdates after drawing the contents
> of the frame, both should appear as one action (we don’t see the blank
> frame at all).

Where does the frame blanking happen in the NS build?

> I’ve tried adding calls to NSDisableScreenUpdates and
> NSEnableScreenUpdates in redisplay_internal, just to see if it works,
> but I couldn’t get it to work at all: I always saw the blanked frame.
> Either these functions don’t work as advertised or there’s something
> else going on. It’s quite probable I’ve misunderstood
> redisplay_internal.

If you tell me where did you try to add these calls and perhaps also
what was your mental model of what redisplay_internal does when you
did that, I might be able to help you add this in the right places
(assuming the idea is workable, and I trust your expertise on that).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.