unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: ***SPAM***  Re: (x-display-pixel-height)
Date: Sun, 22 May 2022 08:57:55 +0300	[thread overview]
Message-ID: <83y1yu6rdo.fsf@gnu.org> (raw)
In-Reply-To: <87k0aes61s.fsf@yahoo.com> (message from Po Lu on Sun, 22 May 2022 09:35:27 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 22 May 2022 09:35:27 +0800
> 
> Hmm, I have a few questions: is it safe to assume the WM_DISPLAYCHANGE
> message will always be defined in the Windows headers Emacs is built
> with, and does it exist on Windows 9x?

Yes, see

  http://winapi.freetechsecrets.com/win32/WIN32WMDISPLAYCHANGE.htm

(which is IME an invaluable resource for finding information about API
support in old versions of Windows that Microsoft don't want us to
know about).

Of course, Windows 9X didn't support multiple monitors or PnP
monitors, so only resolution changes are relevant to those versions.
But I think w32-display-monitor-attributes-list already handles the
old versions gracefully.



  reply	other threads:[~2022-05-22  5:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 22:56 (x-display-pixel-height) Perry Smith
2022-05-19  1:05 ` (x-display-pixel-height) Po Lu
2022-05-19 14:52   ` (x-display-pixel-height) Perry Smith
2022-05-20  1:04     ` (x-display-pixel-height) Po Lu
2022-05-20 16:43       ` ***SPAM*** (x-display-pixel-height) Perry Smith
2022-05-21  1:33         ` Po Lu
2022-05-21  3:19           ` Po Lu
2022-05-21  7:56             ` Eli Zaretskii
2022-05-21  8:24               ` Po Lu
2022-05-21  8:33                 ` Eli Zaretskii
2022-05-21  8:39                   ` Po Lu
2022-05-22  1:35                 ` Po Lu
2022-05-22  5:57                   ` Eli Zaretskii [this message]
2022-05-22  6:18                     ` Po Lu

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=83y1yu6rdo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).