From: Po Lu <luangruo@yahoo.com>
To: Akira Kyle <akira@akirakyle.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Removing the `window-id' frame parameter on non-Core Input platforms
Date: Mon, 20 Dec 2021 11:16:14 +0800 [thread overview]
Message-ID: <87pmps3r0h.fsf@yahoo.com> (raw)
In-Reply-To: <CAPWcbYEUWagu=g4J9o=BjMxFuQ2R+aPLn8YrEAb0EpCG_66Biw@mail.gmail.com> (Akira Kyle's message of "Sun, 19 Dec 2021 19:25:36 -0700")
Akira Kyle <akira@akirakyle.com> writes:
> emacs-webkit uses the pointer obtained via 'window-id' on pgtk builds
> to help identify the correct gtk container widget containing contents
> of the emacs frame that should become the parent of the webkit widget.
> It's a bit of a hack but would be potentially more difficult without
> this pointer.
I'm not sure we want to allow direct access to the innards of how Emacs
utilises GTK widgets. That way lies madness.
> I also know that EAF uses the 'widow-id' parameter on x+gtk builds in
> order to allow Qt widgets to be reparented onto emacs frames.
I've already discussed this with the EAF developers. Until Qt gains the
ability to not select for TouchBegin, TouchUpdate and TouchEnd, EAF will
likely not work on XInput2 builds.
> Also a slight tangent, but Po, do you plan to make xwidgets work on
> pgtk? I'm wondering that since you've been trying to revive the
> xwidget code and fixed the flickering issues on x+gtk, that xwidgets
> are looking more like they are here to stay as a potentially
> non-experimental feature? If that's the case, then I think I'd like to
> then just integrate the work I've done on emacs-webkit into a pgtk
> version of xwidgets? I think one of the key differences between the
> codes are the osr versus one-to-one buffer-webkit view models.
I will work on it eventually, which will be before the release of Emacs
29.
next prev parent reply other threads:[~2021-12-20 3:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y24ifpkj.fsf.ref@yahoo.com>
2021-12-18 5:29 ` Removing the `window-id' frame parameter on non-Core Input platforms Po Lu
2021-12-18 7:22 ` Po Lu
2021-12-18 7:29 ` Eli Zaretskii
2021-12-18 7:53 ` Po Lu
2021-12-18 9:35 ` Eli Zaretskii
2021-12-18 9:40 ` Po Lu
2021-12-18 16:35 ` Stefan Monnier
2021-12-18 16:47 ` [External] : " Drew Adams
2021-12-19 2:48 ` Po Lu
2021-12-19 4:39 ` Stefan Monnier
2021-12-19 5:32 ` Po Lu
2021-12-20 2:25 ` Akira Kyle
2021-12-20 3:16 ` Po Lu [this message]
2021-12-20 3:20 ` Po Lu
2021-12-20 3:34 ` Akira Kyle
2021-12-20 3:39 ` Po Lu
2021-12-20 4:03 ` Akira Kyle
2021-12-20 4:45 ` Po Lu
2021-12-20 22:49 ` Akira Kyle
2021-12-21 1:15 ` Po Lu
2021-12-21 3:23 ` Akira Kyle
2021-12-21 4:38 ` Po Lu
2021-12-21 19:24 ` Akira Kyle
2021-12-20 3:27 ` Akira Kyle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmps3r0h.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=akira@akirakyle.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.