unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Problems implementing double buffered painting for Windows
@ 2020-05-11 10:13 Cecilio Pardo
  2020-05-11 16:49 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Cecilio Pardo @ 2020-05-11 10:13 UTC (permalink / raw)
  To: emacs-devel


Hello,

I'm trying to implement double buffered painting for Windows, to
eliminate flicker. I am encountering some problems:

- When to flip buffers? I have tried to attach the flip to
  frame_up_to_date_hook on the 'terminal' struct, but it sometimes get
  called when it should not, producing flicker.

- What portion of the screen has been updated? I have seen no clear way
  to find this out. I'm resorting to intercept calls to w32_fill_rect to
  mark areas as invalidated, as it /seems/ to be always used to clean
  the area before painting, but this is clearly not a solution.

Any ideas welcome. Thank you.

-- 
Cecilio Pardo



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Problems implementing double buffered painting for Windows
  2020-05-11 10:13 Problems implementing double buffered painting for Windows Cecilio Pardo
@ 2020-05-11 16:49 ` Eli Zaretskii
  2020-05-12  1:40   ` chad
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2020-05-11 16:49 UTC (permalink / raw)
  To: Cecilio Pardo; +Cc: emacs-devel

> From: Cecilio Pardo <cpardo@imayhem.com>
> Date: Mon, 11 May 2020 12:13:50 +0200
> 
> I'm trying to implement double buffered painting for Windows, to
> eliminate flicker.

Thank you very much for working on this.

> - When to flip buffers? I have tried to attach the flip to
>   frame_up_to_date_hook on the 'terminal' struct, but it sometimes get
>   called when it should not, producing flicker.

Did you try doing something similar to what xterm.c does on X?  I mean
the block_buffer_flips trick.  If you did, and it didn't work, why not

> - What portion of the screen has been updated? I have seen no clear way
>   to find this out. I'm resorting to intercept calls to w32_fill_rect to
>   mark areas as invalidated, as it /seems/ to be always used to clean
>   the area before painting, but this is clearly not a solution.

Why not update the entire frame?  That's what the X code does, AFAIU.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Problems implementing double buffered painting for Windows
  2020-05-11 16:49 ` Eli Zaretskii
@ 2020-05-12  1:40   ` chad
  0 siblings, 0 replies; 3+ messages in thread
From: chad @ 2020-05-12  1:40 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: Cecilio Pardo, EMACS development team

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

In addition to Eli's advice, you might find some inspiration in the Mac
port, a version of emacs for macOS that uses a different set of system APIs
than the ns port, which is included in the mainline. It's available
directly via mercurial:
 https://bitbucket.org/mituharu/emacs-mac/src/master/

Hope this helps,
~Chad


On Mon, May 11, 2020 at 9:50 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Cecilio Pardo <cpardo@imayhem.com>
> > Date: Mon, 11 May 2020 12:13:50 +0200
> >
> > I'm trying to implement double buffered painting for Windows, to
> > eliminate flicker.
>
> Thank you very much for working on this.
>
> > - When to flip buffers? I have tried to attach the flip to
> >   frame_up_to_date_hook on the 'terminal' struct, but it sometimes get
> >   called when it should not, producing flicker.
>
> Did you try doing something similar to what xterm.c does on X?  I mean
> the block_buffer_flips trick.  If you did, and it didn't work, why not
>
> > - What portion of the screen has been updated? I have seen no clear way
> >   to find this out. I'm resorting to intercept calls to w32_fill_rect to
> >   mark areas as invalidated, as it /seems/ to be always used to clean
> >   the area before painting, but this is clearly not a solution.
>
> Why not update the entire frame?  That's what the X code does, AFAIU.
>
>

[-- Attachment #2: Type: text/html, Size: 1947 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-05-12  1:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-11 10:13 Problems implementing double buffered painting for Windows Cecilio Pardo
2020-05-11 16:49 ` Eli Zaretskii
2020-05-12  1:40   ` chad

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).