From: Po Lu <luangruo@yahoo.com>
To: Psionic K <psionik@positron.solutions>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Child frame alpha (not background)
Date: Mon, 13 Nov 2023 14:43:41 +0800 [thread overview]
Message-ID: <87msvim9uq.fsf@yahoo.com> (raw)
In-Reply-To: <CADQMGASPeT6N=MSewFVKN80qYw+GZXFx+s-y=dPyW1+n2tznqQ@mail.gmail.com> (Psionic K.'s message of "Mon, 13 Nov 2023 15:36:00 +0900")
[Please use "Reply All", so that the mailing list receives all replies.]
Psionic K <psionik@positron.solutions> writes:
> Sounds like the expectation is that applications should composite
> internally if they want to draw more things in a given window. Given
> that tiling exists, asking for windows but not wanting them managed by
> a window manager seems counter to a user-choice focused data model.
X "windows" are what other toolkits dub "widgets," top-level windows
being windows whose parents are the root window or frame windows created
by a window manager. A window manager cannot control top-level windows
on which the override-redirect property is set, so such constrants as
tiling cannot be imposed on them.
> If that's true, the right solution is to properly implement a child
> frame that uses drawing rather than repurposing the window
> functionality.
Anyway, patches to this end are welcome as always, but until then frames
will remain sub-optimal as user-interface elements.
prev parent reply other threads:[~2023-11-13 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 8:30 Child frame alpha (not background) Psionic K
2023-11-11 12:44 ` Po Lu
[not found] ` <CADQMGASK6TGDJcPOH8jisca6PRbn_KR5tvk=YQ=D10Ftf01LwA@mail.gmail.com>
[not found] ` <87r0kumazp.fsf@yahoo.com>
[not found] ` <CADQMGASPeT6N=MSewFVKN80qYw+GZXFx+s-y=dPyW1+n2tznqQ@mail.gmail.com>
2023-11-13 6:43 ` Po Lu [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=87msvim9uq.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
--cc=psionik@positron.solutions \
/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.
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).