From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55208@debbugs.gnu.org
Subject: bug#55208: 29.0.50; MS-Windows GUI selection dialogs and double-buffering
Date: Sat, 07 May 2022 16:26:39 +0800 [thread overview]
Message-ID: <87tua17npc.fsf@yahoo.com> (raw)
In-Reply-To: <83czgpzt7n.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 May 2022 10:40:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> w32_msg_pump doesn't handle WM_PAINT, so I'm not sure what you mean
> here. Also, AFAIK w32_msg_pump runs in a separate thread, so is it
> safe to call BitBlt from that thread?
Sorry, I meant `w32_msg_pump'. But it should be safe as long as the
painting is done inside the critical section, which protects all
modifications to the paint buffer (and its handle.)
> I do know, but the above issues bother me more, so I didn't yet try
> this.
I tried to explain above, thanks.
next prev parent reply other threads:[~2022-05-07 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 16:03 bug#55208: 29.0.50; MS-Windows GUI selection dialogs and double-buffering Eli Zaretskii
2022-05-02 1:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-02 2:29 ` Eli Zaretskii
2022-05-02 2:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 7:40 ` Eli Zaretskii
2022-05-07 8:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-07 9:02 ` Eli Zaretskii
2022-05-07 9:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 10:06 ` Eli Zaretskii
2022-05-07 10:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 10:41 ` Eli Zaretskii
2022-05-08 5:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 6:26 ` Eli Zaretskii
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=87tua17npc.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55208@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).