unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: martin rudalics <rudalics@gmx.at>,
	Dani Moncayo <dmoncayo@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	25542@debbugs.gnu.org,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#25542: 25.1; Restoring the frame from fullscreen to maximized
Date: Thu, 10 Sep 2020 11:05:24 -0400	[thread overview]
Message-ID: <4869c79f-2f3b-cafb-0459-c6f39f9a6bd5@cornell.edu> (raw)
In-Reply-To: <818f2053-a996-7ade-c1cf-6592b6d2cde5@gmx.at>

On 9/10/2020 3:16 AM, martin rudalics wrote:
>  >> I just tried this on a Cygwin-w32 build from the master branch.  I put the 
> taskbar on the left, started emacs, maximized it, attached gdb, put breakpoints 
> at each of the ShowWindow lines, and ran through Dani's recipe for producing the 
> bug.  The breakpoints were never hit.
>  >
>  > I just tried again, but this time with a breakpoint at w32fullscreen_hook so 
> that I could follow the flow.  Here are the relevant excerpts from the gdb session:
> 
> Thank you very much for checking.
> 
>  > Breakpoint 2 at 0x10069507a: file ../../master/src/w32term.c, line 6441.
>  > (gdb) r -Q
>  > Starting program: /home/kbrown/src/emacs/x86_64-w32/src/emacs -Q
>  >
>  > [...]
>  >
>  > [Press F11]
>  >
>  > Thread 1 "emacs" hit Breakpoint 2, w32fullscreen_hook (f=0x8001f7c88)
>  >      at ../../master/src/w32term.c:6441
> [...]
>  > 6464          FRAME_PREV_FSMODE (f) = f->want_fullscreen;
>  > (gdb) p f->want_fullscreen
>  > $1 = FULLSCREEN_BOTH
> 
> While this is the expected value ...
> 
>  > [...]
>  >
>  > (gdb) c
>  > Continuing.
>  >
>  > [Press F11 again]
>  >
>  > Thread 1 "emacs" hit Breakpoint 2, w32fullscreen_hook (f=0x8001f7c88)
>  >      at ../../master/src/w32term.c:6441
> [...]
>  > 6451          if (FRAME_PREV_FSMODE (f) == FULLSCREEN_NONE)
>  > (gdb) p f->want_fullscreen
>  > $2 = FULLSCREEN_NONE
> 
> ... the value I would have expected here is FULLSCREEN_MAXIMIZED.
> Something must have got broken before.  Can you please
> 
> (1) Verify that the
> 
>        f->want_fullscreen &= ~FULLSCREEN_WAIT;
> 
>      does not interfere in any respect.  That is, does f->want_fullscreen
>      have the same value FULLSCREEN_NONE before anding it with
>      FULLSCREEN_WAIT?

Yes.

> (2) Does 'toggle-frame-fullscreen' the second time when you type F11
>      correctly call
> 
>     (set-frame-parameter frame 'fullscreen fullscreen-restore)
> 
>     with 'fullscreen-restore' equal to 'maximized' at all?

No.  The value of 'fullscreen-restore' is nil.  But if I repeat the experiment 
with the taskbar on the bottom, the value of fullscreen-restore is 'maximized'.

> (3) Verify that calling w32fullscreen_hook with the taskbar on the
>      bottom does hit the breakpoints and subsequently maximize the frame
>      as expected.

With the taskbar on the bottom, f->want_fullscreen == FULLSCREEN_MAXIMIZED when 
I hit line 6449 after the second F11, and everything goes as expected after that.

Ken





  reply	other threads:[~2020-09-10 15:05 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  8:15 bug#25542: 25.1; Restoring the frame from fullscreen to maximized Dani Moncayo
2017-01-26  9:51 ` martin rudalics
2017-01-26 10:20   ` Dani Moncayo
2017-01-26 10:54     ` Dani Moncayo
2017-01-26 17:49       ` Dani Moncayo
2017-01-26 18:02         ` Noam Postavsky
2017-01-26 19:06         ` martin rudalics
2017-01-27  7:54           ` Dani Moncayo
2017-01-27  9:18             ` martin rudalics
2017-01-26 14:00     ` martin rudalics
2017-01-26 15:43       ` Noam Postavsky
2017-01-26 16:10         ` Eli Zaretskii
2017-01-27  8:03       ` Dani Moncayo
2017-01-27  8:16         ` Eli Zaretskii
2017-01-27  8:22           ` Dani Moncayo
2017-01-27  9:19         ` martin rudalics
2017-01-27  9:25           ` Dani Moncayo
2017-01-27  9:31             ` Dani Moncayo
2017-01-27  9:50               ` martin rudalics
2017-01-27 10:22                 ` Dani Moncayo
2017-01-27 10:27                   ` Dani Moncayo
2017-01-27  9:34             ` martin rudalics
2017-01-27 10:01               ` Dani Moncayo
2017-01-27 13:47                 ` martin rudalics
2017-01-27 18:50                   ` Noam Postavsky
2017-01-28  8:02                     ` martin rudalics
2020-09-04 12:32                       ` Lars Ingebrigtsen
2020-09-04 17:50                         ` Dani Moncayo
2020-09-05  6:46                           ` Eli Zaretskii
2020-09-05 11:59                             ` Dani Moncayo
2020-09-05 12:17                               ` Eli Zaretskii
2020-09-05 12:19                                 ` Dani Moncayo
2020-09-05 12:30                                   ` Eli Zaretskii
2020-09-05 12:32                                     ` Dani Moncayo
2020-09-05 12:48                                       ` Eli Zaretskii
2020-09-05 15:10                                       ` Ken Brown
2020-09-05 16:07                                         ` Eli Zaretskii
2020-09-05 16:10                                           ` Ken Brown
2020-09-05 16:41                                             ` Eli Zaretskii
2020-09-09  8:44                               ` martin rudalics
2020-09-09 16:46                                 ` Dani Moncayo
2020-09-09 18:19                                 ` Ken Brown
2020-09-09 20:24                                   ` Ken Brown
2020-09-10  7:16                                     ` martin rudalics
2020-09-10 15:05                                       ` Ken Brown [this message]
2020-09-10 18:16                                         ` martin rudalics
2020-09-10 19:04                                           ` Ken Brown
2020-09-11  7:53                                             ` martin rudalics
2020-09-11 20:16                                               ` Ken Brown
2020-09-11 20:33                                                 ` Achim Gratz
2020-09-11 21:18                                                   ` Ken Brown
2020-09-12  6:54                                                     ` martin rudalics
2020-09-12 11:37                                                       ` Ken Brown
2020-09-12  6:54                                                   ` martin rudalics
2020-09-12  6:06                                                 ` Eli Zaretskii
2020-09-12  6:54                                                 ` martin rudalics
2017-01-26 16:08   ` Eli Zaretskii

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=4869c79f-2f3b-cafb-0459-c6f39f9a6bd5@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=25542@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=npostavs@users.sourceforge.net \
    --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).