From: Ihor Radchenko <yantar92@gmail.com>
To: martin rudalics <rudalics@gmx.at>, 38497@debbugs.gnu.org
Subject: bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't
Date: Sun, 08 Dec 2019 12:41:21 +0800 [thread overview]
Message-ID: <87muc3bf9q.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <25861c90-bdb5-e873-7da7-22a8d997f4b6@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
> Maybe a conversion problem. Does
>
> ew->core.width = (frame_resize_pixelwise
> ? (Dimension) FRAME_PIXEL_WIDTH (f)
> : pixel_width);
> ew->core.height = (frame_resize_pixelwise
> ? (Dimension) FRAME_PIXEL_HEIGHT (f)
> : pixel_height);
>
> yield better results?
It makes no difference.
> ... If not, can you tell me the four values here
> when it fails to redraw - that of FRAME_PIXEL_WIDTH (f), pixel_width,
> FRAME_PIXEL_HEIGHT (f) and pixel_height.
Not sure how to get those.
Anyway, the problem does not seem to be related to the code above.
> This one
>
> - XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 1 : cw),
> - XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 1 : ch),
> + XtNwidthInc, (XtArgVal) (cw),
> + XtNheightInc, (XtArgVal) (ch),
>
> is more mysterious. Why should 1 fail here? What happens when you do
>
> cw = frame_resize_pixelwise ? 1 : cw;
> ch = frame_resize_pixelwise ? 1 : ch;
> XtVaSetValues (wmshell,
> XtNbaseWidth, (XtArgVal) base_width,
> XtNbaseHeight, (XtArgVal) base_height,
> XtNwidthInc, (XtArgVal) cw,
> XtNheightInc, (XtArgVal) ch,
> XtNminWidth, (XtArgVal) base_width,
> XtNminHeight, (XtArgVal) base_height,
> NULL);
>
> instead?
Actually, this piece of code seems to be a more specific reason
triggering the bug (see the relevant patch attached - that patch makes
the bug disappear).
I tried your suggestion (no idea how it is different from original code
though). It makes no difference.
A possible hint to why this code fails to resize the frame is that my
WM resizes the frame as soon as it is created. It is not a gradual
resizing with mouse, but rather instant resize to pre-calculated size
(according to layout). I can sometimes even see the frame being created
with much smaller size for a split second followed by resizing it to
target size.
Best,
Ihor
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: widget-ignore-pixelwise-6.patch --]
[-- Type: text/x-diff, Size: 567 bytes --]
diff --git a/src/widget.c b/src/widget.c
index e8eaf0fadf..4c00e35333 100644
--- a/src/widget.c
+++ b/src/widget.c
@@ -315,8 +315,8 @@ update_wm_hints (EmacsFrame ew)
XtVaSetValues (wmshell,
XtNbaseWidth, (XtArgVal) base_width,
XtNbaseHeight, (XtArgVal) base_height,
- XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 1 : cw),
- XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 1 : ch),
+ XtNwidthInc, (XtArgVal) (cw),
+ XtNheightInc, (XtArgVal) (ch),
XtNminWidth, (XtArgVal) base_width,
XtNminHeight, (XtArgVal) base_height,
NULL);
[-- Attachment #3: Type: text/plain, Size: 3203 bytes --]
martin rudalics <rudalics@gmx.at> writes:
> > The attached patch is the minimal patch making the rendering issue
> > disappear.
>
> Thank you.
>
> > Also, I cannot reproduce the issue when I try to configure
> > emacs just with ./configure --with-x-toolkit=lucid. The options I used
> > to compile emacs in my OS (I am using gentoo) are
> >
> > ./configure --prefix=/usr --build=x86_64-pc-linux-gnu
> > --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
> > --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> > --localstatedir=/var/lib --disable-silent-rules
> > --docdir=/usr/share/doc/emacs-vcs-27.0.9999
> > --htmldir=/usr/share/doc/emacs-vcs-27.0.9999/html --libdir=/usr/lib64
> > --program-suffix=-emacs-27-vcs --includedir=/usr/include/emacs-27-vcs
> > --infodir=/usr/share/info/emacs-27-vcs --localstatedir=/var
> > --enable-locallisppath=/etc/emacs:/usr/share/emacs/site-lisp
> > --without-compress-install --without-hesiod --without-pop
> > --with-dumping=pdumper --with-file-notification=inotify --enable-acl
> > --with-dbus --with-modules --without-gameuser --with-libgmp --with-gpm
> > --without-json --without-kerberos --without-kerberos5 --with-lcms2
> > --with-xml2 --without-mailutils --without-selinux --with-gnutls
> > --without-libsystemd --with-threads --without-wide-int --with-zlib
> > --with-sound=alsa --with-x --without-ns --without-gconf
> > --without-gsettings --without-toolkit-scroll-bars --with-gif --with-jpeg
> > --with-png --with-rsvg --with-tiff --with-xpm --with-imagemagick
> > --with-xft --with-cairo --without-harfbuzz --without-libotf
>
> Is it a good idea to build with xft _and_ cairo? And what's bad
> about libotf?
>
> > --without-m17n-flt --with-x-toolkit=lucid --with-xaw3d
>
> - ew->core.width = (frame_resize_pixelwise
> - ? FRAME_PIXEL_WIDTH (f)
> - : pixel_width);
> - ew->core.height = (frame_resize_pixelwise
> - ? FRAME_PIXEL_HEIGHT (f)
> - : pixel_height);
> + ew->core.width = (pixel_width);
> + ew->core.height = (pixel_height);
>
> Maybe a conversion problem. Does
>
> ew->core.width = (frame_resize_pixelwise
> ? (Dimension) FRAME_PIXEL_WIDTH (f)
> : pixel_width);
> ew->core.height = (frame_resize_pixelwise
> ? (Dimension) FRAME_PIXEL_HEIGHT (f)
> : pixel_height);
>
> yield better results? If not, can you tell me the four values here
> when it fails to redraw - that of FRAME_PIXEL_WIDTH (f), pixel_width,
> FRAME_PIXEL_HEIGHT (f) and pixel_height.
>
> This one
>
> - XtNwidthInc, (XtArgVal) (frame_resize_pixelwise ? 1 : cw),
> - XtNheightInc, (XtArgVal) (frame_resize_pixelwise ? 1 : ch),
> + XtNwidthInc, (XtArgVal) (cw),
> + XtNheightInc, (XtArgVal) (ch),
>
> is more mysterious. Why should 1 fail here? What happens when you do
>
> cw = frame_resize_pixelwise ? 1 : cw;
> ch = frame_resize_pixelwise ? 1 : ch;
> XtVaSetValues (wmshell,
> XtNbaseWidth, (XtArgVal) base_width,
> XtNbaseHeight, (XtArgVal) base_height,
> XtNwidthInc, (XtArgVal) cw,
> XtNheightInc, (XtArgVal) ch,
> XtNminWidth, (XtArgVal) base_width,
> XtNminHeight, (XtArgVal) base_height,
> NULL);
>
> instead?
>
> martin
next prev parent reply other threads:[~2019-12-08 4:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 7:08 bug#38497: 27.0.50; Frame is not rendered when frame-resize-pixelwise it 't 'Ihor Radchenko'
2019-12-05 9:10 ` martin rudalics
2019-12-05 10:21 ` Ihor Radchenko
2019-12-05 13:45 ` martin rudalics
2019-12-07 13:35 ` Ihor Radchenko
2019-12-07 16:29 ` martin rudalics
2019-12-07 16:58 ` Ihor Radchenko
2019-12-08 8:57 ` martin rudalics
2019-12-08 9:24 ` Ihor Radchenko
2019-12-09 9:20 ` martin rudalics
2019-12-13 7:18 ` Ihor Radchenko
2019-12-13 7:18 ` Ihor Radchenko
2019-12-13 7:03 ` Ihor Radchenko
2019-12-13 9:35 ` martin rudalics
2019-12-13 11:42 ` Ihor Radchenko
2019-12-13 15:57 ` martin rudalics
2019-12-13 16:46 ` Ihor Radchenko
2019-12-14 9:06 ` martin rudalics
2019-12-14 9:38 ` Ihor Radchenko
2019-12-14 11:40 ` Eli Zaretskii
2019-12-14 12:22 ` Ihor Radchenko
2019-12-14 13:36 ` Eli Zaretskii
2019-12-15 13:43 ` Ihor Radchenko
2019-12-15 15:21 ` Eli Zaretskii
2019-12-16 3:10 ` Ihor Radchenko
2019-12-16 3:33 ` Eli Zaretskii
2019-12-14 9:39 ` Ihor Radchenko
2019-12-14 10:16 ` Ihor Radchenko
2019-12-14 13:24 ` martin rudalics
2019-12-15 13:57 ` Ihor Radchenko
2019-12-15 17:42 ` martin rudalics
[not found] ` <87mubtngt7.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>
2019-12-16 9:14 ` martin rudalics
2019-12-16 10:53 ` mituharu
2019-12-16 13:04 ` Ihor Radchenko
2019-12-16 15:36 ` Eli Zaretskii
2019-12-17 0:39 ` Ihor Radchenko
2019-12-17 6:50 ` YAMAMOTO Mitsuharu
2019-12-17 10:37 ` Ihor Radchenko
2020-01-06 9:19 ` YAMAMOTO Mitsuharu
2020-01-06 10:57 ` Ihor Radchenko
2020-01-07 3:52 ` YAMAMOTO Mitsuharu
2019-12-08 4:41 ` Ihor Radchenko [this message]
2019-12-08 8:57 ` martin rudalics
2019-12-08 9:21 ` Ihor Radchenko
2019-12-09 9:19 ` martin rudalics
2019-12-09 9:55 ` Ihor Radchenko
2019-12-09 15:59 ` martin rudalics
2019-12-13 7:19 ` Ihor Radchenko
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=87muc3bf9q.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=yantar92@gmail.com \
--cc=38497@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).