GNU bug report logs - #23925
25.0.95; cairo: display broken when maximizing frames

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Clément Pit--Claudel <clement.pit <at> gmail.com>,  23925 <at> debbugs.gnu.org, Roland Winkler <winkler <at> gnu.org>
Subject: bug#23925: 25.0.95; display broken when maximizing frame
Date: Mon, 11 Jul 2016 11:14:03 +0200

Clément:

> (((name . "DP-2") (geometry 0 0 1920 1080) (workarea 0 0 1920 1055) (mm-size 344 193) (frames #<frame **scratch* 0x12bb5a0>) (source . "Gdk")))

> ((outer-position 0 . 0) (outer-size 1920 . 1055) (external-border-size 0 . 1) (title-bar-size 0 . 23) (menu-bar-external . t) (menu-bar-size 0 . 0) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 0))

> frame pixel: 1920 x 1030   cols/lines: 240 x 64   units: 8 x 16
> frame text pixel: 1904 x 1030   cols/lines: 238 x 64
> tool: 0  scroll: 0/0  fringe: 16  border: 0  right: 0  bottom: 0
>
> #<window 3 on *scratch*>   parent: nil
> pixel left: 0   top: 0   size: 1920 x 1014   new: 669
> char left: 0   top: 0   size: 240 x 63   new: 84
> normal: 1.0 x 1.0   new: 1.0
> body pixel: 1904 x 979   char: 238 x 61
> width left fringe: 8  left margin: 0  right margin: 0
> width right fringe: 8  scroll-bar: 0  divider: 0
> height header-line: 16  mode-line: 19  divider: 0
>
> #<window 4 on  *Minibuf-0*>   parent: nil
> pixel left: 0   top: 1014   size: 1920 x 16   new: 0
> char left: 0   top: 63   size: 240 x 1   new: 84
> normal: 1.0 x 1.0   new: ignore
> body pixel: 1904 x 16   char: 238 x 1
> width left fringe: 8  left margin: 0  right margin: 0
> width right fringe: 8  scroll-bar: 0  divider: 0
> height header-line: 0  mode-line: 0  divider: 0


Roland:

> (((name . "DP2") (geometry 0 0 1920 1080) (workarea 0 25 1920 1055) (mm-size 510 287) (frames #<frame emacs <at> regnitz 0x1244a90>) (source . "Gdk")))

> ((outer-position 0 . 25) (outer-size 1913 . 1052) (external-border-size 5 . 5) (title-bar-size 0 . 18) (menu-bar-external . t) (menu-bar-size 1903 . 22) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))

> frame pixel: 1903 x 1002   cols/lines: 191 x 50   units: 10 x 20
> frame text pixel: 1870 x 1000   cols/lines: 187 x 50
> tool: 0  scroll: 15/0  fringe: 16  border: 1  right: 0  bottom: 0
>
> #<window 3 on *Messages*>   parent: nil
> pixel left: 0   top: 0   size: 1901 x 980   new: 820
> char left: 0   top: 0   size: 190 x 49   new: 38
> normal: 1.0 x 1.0   new: nil
> body pixel: 1870 x 960   char: 187 x 48
> width left fringe: 8  left margin: 0  right margin: 0
> width right fringe: 8  scroll-bar: 15  divider: 0
> height header-line: 0  mode-line: 20  divider: 0
>
> #<window 4 on  *Minibuf-0*>   parent: nil
> pixel left: 0   top: 980   size: 1901 x 20   new: 0
> char left: 0   top: 49   size: 190 x 1   new: 1
> normal: 1.0 x 1.0   new: 0
> body pixel: 1870 x 20   char: 187 x 1
> width left fringe: 8  left margin: 0  right margin: 0
> width right fringe: 8  scroll-bar: 15  divider: 0
> height header-line: 0  mode-line: 0  divider: 0


All these values are as expected - I suppose that they are the same as
in a non-cairo GTK session.  What happens when you type F11
(‘toggle-frame-fullscreen’) in a normal frame?  Also, could one of you
try a Lucid or Motif build with cairo and see what happens?

martin

Previous Next

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