unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Subject: Re: Removing the `window-id' frame parameter on non-Core Input platforms
Date: Sat, 18 Dec 2021 15:22:53 +0800	[thread overview]
Message-ID: <87r1aafkc2.fsf@yahoo.com> (raw)
In-Reply-To: <87y24ifpkj.fsf@yahoo.com> (Po Lu's message of "Sat, 18 Dec 2021 13:29:48 +0800")

Po Lu <luangruo@yahoo.com> writes:

> The only platform where it is useful is X with Core Input, where third
> party programs can use it to manipulate a frame's X Window.
>
> This is safe on Core Input, but on XInput 2 I'd like the freedom to
> change the underlying X window of a frame after it is created to work
> around some difficult GTK related problems, which will make continuing
> to support the `window-id' parameter unreasonable.  Touch event tracking
> on XInput2 also requires that no non-Emacs code modify a window created
> by Emacs to work correctly.
>
> On non-X platforms, `window-id' is just a pointer which is even more
> useless, so I'd like to make this code in frame.c conditional on
> HAVE_X_WINDOWS && !HAVE_XINPUT2:
>
>   w = (uintptr_t) FRAME_NATIVE_WINDOW (f);
>   store_in_alist (alistptr, Qwindow_id,
> 		  make_formatted_string (buf, "%"PRIuMAX, w));
>
> Does that look OK to you?

The problem this proposal was supposed to solve turned out to be
specific to a version of GNOME Shell, so I added an entry in
etc/PROBLEMS instead.

Please disregard this message.



  reply	other threads:[~2021-12-18  7:22 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 [this message]
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
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

  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=87r1aafkc2.fsf@yahoo.com \
    --to=luangruo@yahoo.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 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).