From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18637@debbugs.gnu.org
Subject: bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows
Date: Mon, 6 Oct 2014 10:25:31 -0700 (PDT) [thread overview]
Message-ID: <c75b3094-d24b-4949-9c1e-b513c0b5bed7@default> (raw)
In-Reply-To: <<837g0dm95c.fsf@gnu.org>>
> > > In any case, "multiple monitors" and "multiple displays" are 2
> > > different issues. Each display can have multiple monitors.
> >
> > OK. Where can one find doc about using multiple monitors with
> > Emacs?
>
> There's nothing to document: they are treated as just one large
> monitor. The only functions we have are in that node you mentioned.
>
> > > > I was not able to find out how to obtain info about which
> > > > monitor is being used to show a particular frame
> > >
> > > The functions you mentioned provide that info, or maybe I don't
> > > understand what info are you looking for.q
> >
> > Which function tells you what monitor is showing a given frame (on
> > MS Windows)?
>
> frame-monitor-attributes, if I understand what you want.
I see that that function returns some information about (attributes
of) the monitor that is most associated with the argument frame. And
I see that one of the attributes is `name'. Presumably, monitors
would be distinguished by this parameter.
However, it is an optional parameter, so I can't imagine that one can
count on it to distinguish monitors. (Just why is it optional?)
If one cannot count on `name', how is the identity of monitors
determined? Do you just go by the particular cons of attributes
that is returned by `frame-monitor-attributes'?
Also, FWIW, I don't see, in the doc, where the meanings of those
attributes are specified. The doc for `display-monitor-attributes'
supposedly does that, but it says nothing about what the "Position",
for `geometry' and `workarea', is relative to. And it says nothing
about what those attributes mean.
I can guess the meaning for `geometry' here, being somewhat familiar
with X window `geometry' specs, but there should be some mention or
xref to the meaning/use of `geometry' outside Emacs, or else this
parameter is unspecified in terms of its meaning or effect.
And I cannot guess at all for `workarea'. What is it? How does/can
it differ from `geometry'?
> > > > The symptom reported was that by modifying a frame's
> > > > parameters to restore its previous values of `top', `left',
> > > > `width' and `height', the frame got moved to another monitor,
> > > > for some reason.
> > >
> > > Probably because the pixel coordinates mapped to that other
> > > monitor, the URL above explains that, among other things.
> >
> > I appreciate your replies and your trying to help, but I don't
> > quite understand you here. The URL you cite introduces a long
> > chapter.
>
> Read it and its sections. You will find the information you want
> there. Skip whatever sounds not relevant or too low-level, and keep
> reading. Read the MSDN documentation I pointed to, the answers are there.
>
> If, after that, you still don't understand what could go wrong with
> your code, come back and ask more specific questions with specific
> code snippets. Right now, what you write and ask just shows how
> much of the background you are missing to start reasoning about this.
>
> The issues are not complicated once you understand how Windows
> treats multiple monitors.
OK.
next parent reply other threads:[~2014-10-06 17:25 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 ` Drew Adams [this message]
2014-10-05 19:23 ` bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c75b3094-d24b-4949-9c1e-b513c0b5bed7@default \
--to=drew.adams@oracle.com \
--cc=18637@debbugs.gnu.org \
--cc=eliz@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 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.