GNU bug report logs - #67753
28.2, 29.1: Making frame invisible always affects frame position parameters

Previous Next

Full log

Message #29 received at 67753 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 67753 <at> debbugs.gnu.org, soliidne <at> gmail.com
Subject: Re: bug#67753: 28.2, 29.1: Making frame invisible always affects
 frame position parameters
Date: Sat, 20 Jan 2024 17:36:58 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

> Po Lu, any comments or suggestions on this matter?
>
>> From: soliidne <at> gmail.com
>> Date: Wed, 10 Jan 2024 12:25:19 +0200
>> Cc: Po Lu <luangruo <at> yahoo.com>, 67753 <at> debbugs.gnu.org
>> 
>> Hi !
>> 
>> Probable bug in void xfns.c → x_real_pos_and_offsets interpreting _NET_FRAME_EXTENTS set in
>> Application Window Properties by WM.
>> 
>> Current visible Emacs frame parameters:
>> 
>> _NET_FRAME_EXTENTS(CARDINAL) = 5, 5, 29, 5
>> 
>> That means these are Emacs frame border and frame title thicknesses.
>> 
>> The Window Manager MUST set _NET_FRAME_EXTENTS to the extents of the window's frame.
>> left, right, top and bottom are widths of the respective borders added by the Window Manager.

Would you please elaborate on the nature of the bug you perceive?  I get
the impression that you're referring to x_real_pos_and_offsets's
consulting this property in itself, but that is no bug, since the
offsets are not returned as the frame's left and top coordinates, but
are subtracted from its position relative to the root window as
determined from calls to XTranslateCoordinates and XGetGeometry instead.

Unfortunately there is a backlog of X window management related issues I
cannot investigate at the moment, so any input would be appreciated, or
rather, more so than in the past.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.