From: chad <yandros@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Cecilio Pardo <cpardo@imayhem.com>,
EMACS development team <emacs-devel@gnu.org>
Subject: Re: Problems implementing double buffered painting for Windows
Date: Mon, 11 May 2020 18:40:31 -0700 [thread overview]
Message-ID: <CAO2hHWYpJUw2W9e-9vdNxddNxpZ1DDhBEoYcu5dwxjXnLDyrLw@mail.gmail.com> (raw)
In-Reply-To: <833686bens.fsf@gnu.org>
[-- 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 --]
prev parent reply other threads:[~2020-05-12 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO2hHWYpJUw2W9e-9vdNxddNxpZ1DDhBEoYcu5dwxjXnLDyrLw@mail.gmail.com \
--to=yandros@gmail.com \
--cc=cpardo@imayhem.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).