From: Po Lu <luangruo@yahoo.com>
To: xenodasein@tutanota.de
Cc: chad <yandros@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Björn Bidar" <bjorn.bidar@thaodan.de>,
emacs-devel@gnu.org
Subject: Re: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning
Date: Tue, 06 Dec 2022 21:24:39 +0800 [thread overview]
Message-ID: <87mt80mzqg.fsf@yahoo.com> (raw)
In-Reply-To: <NIbX_Nc--F-9@tutanota.de> (xenodasein@tutanota.de's message of "Tue, 6 Dec 2022 14:05:14 +0100 (CET)")
xenodasein@tutanota.de writes:
> Xlib uses XCB underneath anyway, what is this shortsightedness about?
Because you cannot give ownership of the event queue to Xlib if the
connection to the display was obtained through XCB. As a result, Qt has
had to move from only using XCB to using both Xlib and XCB for the two
libraries that are much better than their XCB counterparts: the direct
rendering GLX library and the XInput client library.
You have to understand that Xlib uses XCB only as an underlying
transport. It encodes all requests and reads events solely by itself,
with occasional hooks into XCB to synchronize i.e. the request serial
used (see the calls to xcb_take_socket.) No matter whether or or not
_XSend, _XReadEvents, _XRead, _XReadPad or _XEatDataWords is implemented
on top of XCB, Xlib is still the only library reading events.
next prev parent reply other threads:[~2022-12-06 13:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:38 Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Björn Bidar
2022-11-27 0:48 ` Po Lu
2022-11-28 0:09 ` Björn Bidar
2022-11-28 1:17 ` Po Lu
2022-11-28 8:44 ` Björn Bidar
2022-11-28 11:41 ` Po Lu
2022-11-30 9:27 ` xenodasein--- via Emacs development discussions.
2022-11-30 10:13 ` Po Lu
2022-11-30 12:50 ` Stefan Monnier
2022-11-30 13:39 ` Po Lu
2022-11-30 16:50 ` Stefan Monnier
2022-12-01 0:52 ` Po Lu
2022-12-01 0:56 ` Stefan Monnier
2022-12-01 2:38 ` Po Lu
2022-12-01 5:24 ` Stefan Monnier
2022-12-01 6:45 ` Po Lu
2022-12-05 20:01 ` chad
2022-12-06 11:39 ` Po Lu
2022-12-06 13:05 ` xenodasein--- via Emacs development discussions.
2022-12-06 13:24 ` Po Lu [this message]
2022-12-01 10:25 ` Manuel Giraud
2022-12-01 12:44 ` Visuwesh
[not found] ` <87cz94vjgl.fsf@yahoo.com-NI70zP3----9>
2022-11-30 11:51 ` xenodasein--- via Emacs development discussions.
2022-11-30 13:37 ` Po Lu
2022-11-30 14:00 ` xenodasein--- via Emacs development discussions.
2022-11-30 14:09 ` Po Lu
2022-11-30 15:51 ` xenodasein--- via Emacs development discussions.
2022-12-01 0:49 ` Po Lu
2022-11-30 16:23 ` Eli Zaretskii
2022-11-30 16:56 ` xenodasein--- via Emacs development discussions.
2022-11-30 17:43 ` Eli Zaretskii
2022-12-12 23:52 ` Björn Bidar
2022-12-13 1:22 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 6:33 Pedro Andres Aranda Gutierrez
2022-11-29 6:43 ` Po Lu
2022-11-29 9:36 ` Björn Bidar
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=87mt80mzqg.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=xenodasein@tutanota.de \
--cc=yandros@gmail.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).