unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: 18637@debbugs.gnu.org
Subject: bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows
Date: Tue, 07 Oct 2014 19:35:28 +0100	[thread overview]
Message-ID: <vz11tqjpw27.fsf@gmail.com> (raw)
In-Reply-To: <12fc196e-cc82-4f22-8d2f-cede95542ea7@default>

On Tue 07 Oct 2014, Eli Zaretskii wrote:

>> The relevant code snippet is what I sent earlier
>> (`frcmds-available-screen-pixel-bounds'), plus functions
>> `maximize-frame' and `restore-frame', here:
>> http://www.emacswiki.org/emacs-en/download/frame-cmds.el> 
>> In those two commands I do the following.
>> 
>> For `maximize-frame':
>> 
>> 1. Save the current `left' etc. as parameters `restore-left' etc.
>> 2. Calculate the available screen size, using
>>    `frcmds-available-screen-pixel-bounds'.
>> 3. Set `left' and `top' both to 0 and `width' and `height' to the
>>    calculated screen size.
>> 
>> For `restore-frame':
>> 
>> Restore `left' etc. from the saved values `restore-left' etc.
>
> That's a lot of code, and I have no way of trying it.

I have a multi-monitor system, but I'm not going to perform experiments
without a clearer recipe. I did try rearranging the physical monitor
layout as follows (which makes it quite easy to lose the position of the
cursor). Things may get more confusing with three or more monitors...

;; Two monitors arranged physically as:
;;  +---------+
;;  |         |
;;  |    2    |+---------+
;;  |         ||         |
;;  +---------+|    1    |
;;             |         |
;;             +---------+
(display-monitor-attributes-list)
;; ==>
(((geometry 0 0 1920 1080)
  (workarea 0 0 1920 1050)
  (mm-size 677 381)
  (name . "\\\\.\\DISPLAY1")
  (frames))
 ((geometry -1680 -646 1680 1050)
  (workarea -1680 -646 1680 1050)
  (mm-size 593 370)
  (name . "\\\\.\\DISPLAY2")
  (frames)))

(display-pixel-height)  ;; ==> 1726
(display-pixel-width)   ;; ==> 3600

(display-mm-height)     ;; ==>  609
(display-mm-width)      ;; ==> 1269

> I think at this stage it is best for the user in question to try some
> simple code that reports frame coordinates and creates a frame given
> specific coordinates, and then see what that means for us.
>
> Oh, and I think this is no longer about the docs, so probably a new
> bug report is in order, specifically about restoring frames on
> multi-monitor displays.

True, as long as the meaning of geometry/workarea and the coordinate
system are given a little more detail in the docs.

    AdnyM






  parent reply	other threads:[~2014-10-07 18:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<b5ac6ce3-5c0d-4517-a44f-6925cfccdcfd@default>
     [not found] ` <<837g0dm95c.fsf@gnu.org>
2014-10-06 17:25   ` bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows Drew Adams
2014-10-05 19:23     ` Drew Adams
2014-10-05 19:30       ` Eli Zaretskii
2014-10-05 19:44         ` Eli Zaretskii
2014-10-06 18:08       ` Andy Moreton
2014-10-06 18:23         ` Drew Adams
2014-10-07 18:35       ` Andy Moreton [this message]
2014-10-07 20:25         ` Drew Adams
2014-10-06 19:29     ` Eli Zaretskii
2014-10-06 20:52     ` Drew Adams
2014-10-07 15:14       ` Eli Zaretskii
     [not found] <<c75b3094-d24b-4949-9c1e-b513c0b5bed7@default>
     [not found] ` <<ce89167f-4906-496e-9ace-4d51e1741311@default>
     [not found]   ` <<83tx3flxn2.fsf@gnu.org>
2014-10-07 18:12     ` Drew Adams
2014-10-07 18:26       ` Eli Zaretskii
     [not found]     ` <<41484edb-9aaa-4f56-bf46-4ab70b609aac@default>
     [not found]       ` <<8361fvlos0.fsf@gnu.org>
2014-10-07 18:31         ` Drew Adams
     [not found] <<b3d0f532-3b29-43d3-a41d-6687886307dc@default>
     [not found] ` <<83ppe5mfed.fsf@gnu.org>
2014-10-06 16:31   ` Drew Adams
2014-10-06 16:54     ` Eli Zaretskii
     [not found] <<12fc196e-cc82-4f22-8d2f-cede95542ea7@default>
     [not found] ` <<83vbnymi0h.fsf@gnu.org>
     [not found]   ` <<83tx3imhdg.fsf@gnu.org>
2014-10-06  2:55     ` Drew Adams
2014-10-06 14:39       ` Eli Zaretskii
2014-10-06 16:34         ` Stefan Monnier
2014-10-06  2:55   ` Drew Adams

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=vz11tqjpw27.fsf@gmail.com \
    --to=andrewjmoreton@gmail.com \
    --cc=18637@debbugs.gnu.org \
    /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).