From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=E9=99=88=E5=AE=87=E8=BF=AA?= Newsgroups: gmane.emacs.bugs Subject: bug#65183: 29.1; Child frame moving and resizing problems Date: Fri, 11 Aug 2023 09:01:52 +0100 Message-ID: References: <837cq3jmyk.fsf@gnu.org> <13c2f66e-861d-2ab3-6405-a2b57b29863b@gmx.at> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c9e4180602a12047" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20325"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , 65183@debbugs.gnu.org, Eli Zaretskii To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 11 11:39:31 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qUOcE-00052n-Oo for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 11 Aug 2023 11:39:30 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qUObv-0008A0-UB; Fri, 11 Aug 2023 05:39:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qUObn-00089d-3r for bug-gnu-emacs@gnu.org; Fri, 11 Aug 2023 05:39:07 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qUObm-0005Yc-5W for bug-gnu-emacs@gnu.org; Fri, 11 Aug 2023 05:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qUObm-0006it-1f for bug-gnu-emacs@gnu.org; Fri, 11 Aug 2023 05:39:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=E9=99=88=E5=AE=87=E8=BF=AA?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 11 Aug 2023 09:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65183 X-GNU-PR-Package: emacs Original-Received: via spool by 65183-submit@debbugs.gnu.org id=B65183.169174670325793 (code B ref 65183); Fri, 11 Aug 2023 09:39:02 +0000 Original-Received: (at 65183) by debbugs.gnu.org; 11 Aug 2023 09:38:23 +0000 Original-Received: from localhost ([127.0.0.1]:44921 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qUOb9-0006hw-4G for submit@debbugs.gnu.org; Fri, 11 Aug 2023 05:38:23 -0400 Original-Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]:60762) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qUN61-0001hD-0W for 65183@debbugs.gnu.org; Fri, 11 Aug 2023 04:02:11 -0400 Original-Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-56d0d7300d9so1370138eaf.1 for <65183@debbugs.gnu.org>; Fri, 11 Aug 2023 01:02:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691740923; x=1692345723; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=A1VDkcUi8+yVEhGlQ6b9xohKKyIp6bA30NhNd7MLRZ0=; b=ggD8DxgGq+xOJiYd0BSdwBQTBurp9XhbQYsxreJSFvWZsTb5wngQb4+FSyzi/wh8Lq pmYQ25secdG1cXWcebCiGBEjJPmM/y2k0kJhICZEmBK4Gfsis0qnQMB44lHqfDgTqhrE sEbNDRoeOFnmdMoAoa5kWgE6eeKL2UHJclh6//YoW+mSenlc0CDKmQ0CDL0LhGrvfjn9 8qAOY6DTk4QdsOw0usvDPbBXMxg9o/pHahY9za7sjo2/nUCNEpBAqoOkMWu2I3zeuWl0 Em7f1mTlhCPh8aYf/bKIA5sHsmVsaPn2DlNgmY6EItjNycK3qeiLKXtA+fdaN/PjuI9h NOhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691740923; x=1692345723; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=A1VDkcUi8+yVEhGlQ6b9xohKKyIp6bA30NhNd7MLRZ0=; b=XWQMbLH/D526vQjaQ3MCDbeqDhp5AxfB+UX0AiWut5lRr2nBxnsouI3gIpu4r90xgp oKSqzLkAo7a419LGAlE6/Tkv+xv2Kv5dFlxpNU0ejTHPSS2JwXNfPpdu/y9L5QDE0f7O UjtRF1B4PdtYubNz5FCdHcmFVAN7My+8Vn50CzYi0WWq9hA+aSHyJopvcttQMj4IDvLq lmP6wwGg5F5Bp+P/ixj84FqSuafrenfHpDFVG8q1/D7ZXQK5G7zurNOXa97qKAGYemd6 VNOjnhVx5btsVgC0NP+3hgNpYIi5LVogY0ffT043cjg4BVQl01OIBJOZ/NJYqKfQvzfj 56mw== X-Gm-Message-State: AOJu0Yxm8A60u+Lhm28p0qhltSMdHH7SRtIMEcQwWqp7RJcQSUXouH0O M86ssa/ICcGsx0o6EEYw85Xi9U+P3oj81sk/DgI= X-Google-Smtp-Source: AGHT+IH+WiuJ1PVIbxww13enCV22gyXtamH8HDqbfq2+ZygLeu6C4M73ToGWvyh+8incp4dQqJxqtG1xjLDqXvuYefQ= X-Received: by 2002:a05:6871:68b:b0:1bf:607:e0ed with SMTP id l11-20020a056871068b00b001bf0607e0edmr1279472oao.39.1691740923354; Fri, 11 Aug 2023 01:02:03 -0700 (PDT) In-Reply-To: <13c2f66e-861d-2ab3-6405-a2b57b29863b@gmx.at> X-Mailman-Approved-At: Fri, 11 Aug 2023 05:38:21 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:267201 Archived-At: --000000000000c9e4180602a12047 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It seems that variables `x-gtk-resize-child-frames' and `x-gtk-use-window-move' do not help with this. I am using KDE with KWin (X11) version 5.27.7. I don't know where there is any known issue on this platform. >From another perspective, is there a way to perform resize and move at the same time? (I mean, could the two steps be executed within a single redisplay cycle, so that users would not see the intermediate changes?) If these two steps are not done separately, the execution order would not matter. As I wrote in my first email, I can see the child frame being moved and then resized on my computer, even though the two steps happen very quickly. martin rudalics =E4=BA=8E2023=E5=B9=B48=E6=9C=8811=E6=97= =A5=E5=91=A8=E4=BA=94 08:06=E5=86=99=E9=81=93=EF=BC=9A > >> 2. In the code I gave, `set-frame-size' should be executed before > `set-frame-position'. > >> But in fact, the child frame was first moved, and then resized. It is > in the wrong order. > > > > I don't think you can trust the order in this case, as at least some > > of the actual move/resize is performed by the window-manager. > > ... and Emacs only fills its text into the areas provided and exposed by > the window manager. As a rule, never trust the order of execution in > such case. Resizing child frames is already tricky enough with GTK3 and > some window managers. We have the variable 'x-gtk-resize-child-frames' > for that but setting it shouldn't change anything in the case at hand. > Neither should 'x-gtk-use-window-move' help but you can still try. > > martin > --000000000000c9e4180602a12047 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It seems that variables `x-gtk-resiz= e-child-frames' and `x-gtk-use-window-move' do not help with this.<= /div>
I am using KDE with KWin (X11) version 5.27.7. I don't know w= here there is any known issue on this platform.

From another perspective, is there a way t= o perform resize and move at the same time?
=
(I mean, could the two steps be exe= cuted within a single redisplay cycle,=C2=A0
so that users would not see the = intermediate changes?)
If these two steps are not = done separately, the execution order would not matter.=
As I wrote in my first email, I can see the child frame being mo= ved and then resized
on my computer, even though the two step= s happen very quickly.

martin rudalics <rudalics@gmx.at> =E4=BA=8E2023=E5=B9=B48=E6=9C=8811=E6= =97=A5=E5=91=A8=E4=BA=94 08:06=E5=86=99=E9=81=93=EF=BC=9A
=C2=A0>> 2. In the code I g= ave, `set-frame-size' should be executed before `set-frame-position'= ;.
=C2=A0>> But in fact, the child frame was first moved, and then resiz= ed. It is in the wrong order.
=C2=A0>
=C2=A0> I don't think you can trust the order in this case, as at le= ast some
=C2=A0> of the actual move/resize is performed by the window-manager.
... and Emacs only fills its text into the areas provided and exposed by the window manager.=C2=A0 As a rule, never trust the order of execution in<= br> such case.=C2=A0 Resizing child frames is already tricky enough with GTK3 a= nd
some window managers.=C2=A0 We have the variable 'x-gtk-resize-child-fr= ames'
for that but setting it shouldn't change anything in the case at hand.<= br> Neither should 'x-gtk-use-window-move' help but you can still try.<= br>
martin
--000000000000c9e4180602a12047--