unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ahyatt@gmail.com, lennart.borgman@gmail.com, 5482@debbugs.gnu.org
Subject: bug#5482: frame-invisible-p reports nil for iconified frames on w32
Date: Mon, 27 Jun 2016 08:22:06 +0200	[thread overview]
Message-ID: <5770C60E.20502@gmx.at> (raw)
In-Reply-To: <83bn2oymah.fsf@gnu.org>

 > As for the second issue, I disagree that this behavior is wrong,
 > because it matches the documentation:
 >
 >    A frame on a graphical display may be “visible”, “invisible”, or
 >    “iconified”.  If it is visible, its contents are displayed in the usual
 > 		^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >    manner.  If it is iconified, its contents are not displayed, but there
 >    ^^^^^^
 >    is a little icon somewhere to bring the frame back into view (some
 >    window managers refer to this state as “minimized” rather than
 >    “iconified”, but from Emacs’ point of view they are the same thing).  If
 >    a frame is invisible, it is not displayed at all.
 >
 >     -- Command: make-frame-visible &optional frame
 >         This function makes frame FRAME visible.
 >
 > So I see no reason to fix anything in what make-frame-visible does in
 > this case.

Neither do I.  Emacs implements just a subset of the states and
transitions provided by the Windows API.

 > I could perhaps agree that iconify-frame should have undone the effect
 > of make-frame-invisible in this use case, though.

I see no problems with

(progn
   (setq my-frame (make-frame))
   (make-frame-invisible my-frame)
   (sit-for 1)
   (iconify-frame my-frame)
   (sit-for 1)
   (frame-visible-p my-frame))

Or what did you have in mind?

martin






  reply	other threads:[~2016-06-27  6:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 20:37 bug#5482: frame-invisible-p reports nil for iconified frames on w32 Lennart Borgman
2016-06-26  3:56 ` Andrew Hyatt
2016-06-26 10:18   ` martin rudalics
2016-06-26 15:58     ` Eli Zaretskii
2016-06-27  6:22       ` martin rudalics [this message]
2016-06-27 15:40         ` Eli Zaretskii
2016-06-27 16:56           ` martin rudalics
2016-06-28 16:00             ` Eli Zaretskii
2018-06-14  0:48         ` Noam Postavsky

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=5770C60E.20502@gmx.at \
    --to=rudalics@gmx.at \
    --cc=5482@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=eliz@gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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).