all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Ken Brown <kbrown@cornell.edu>, 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 09:16:01 +0200	[thread overview]
Message-ID: <818f2053-a996-7ade-c1cf-6592b6d2cde5@gmx.at> (raw)
In-Reply-To: <56ee5ed9-fd85-b5c3-6aba-d51332398f03@cornell.edu>

 >> 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?

(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?

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

Thanks again, martin





  reply	other threads:[~2020-09-10  7:16 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 [this message]
2020-09-10 15:05                                       ` Ken Brown
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=818f2053-a996-7ade-c1cf-6592b6d2cde5@gmx.at \
    --to=rudalics@gmx.at \
    --cc=25542@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=kbrown@cornell.edu \
    --cc=larsi@gnus.org \
    --cc=npostavs@users.sourceforge.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.