unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Andy Moreton <andrewjmoreton@gmail.com>, 34516@debbugs.gnu.org
Subject: bug#34516: Multi-monitor frame sets
Date: Mon, 04 Mar 2019 10:52:09 +0100	[thread overview]
Message-ID: <m2ef7n2chi.fsf@gmail.com> (raw)
In-Reply-To: <20190303114324.GA49402@breton.holly.idiocy.org> (Alan Third's message of "Sun, 3 Mar 2019 11:43:24 +0000")

Alan Third <alan@idiocy.org> writes:

> On Sat, Mar 02, 2019 at 11:57:35PM +0000, Andy Moreton wrote:
>> On Sat 02 Mar 2019, Alan Third wrote:
>> 
>> > On Sun, Feb 24, 2019 at 01:56:31PM +0100, Robert Pluim wrote:
>> >> Juri Linkov <juri@linkov.net> writes:
>> >> 
>> >> > on macOS it could return something like that or generate fake names
>> >> > from geometry like "1920x1080+0+0", "2560x1440+1920+16".
>> 
>> It would be more usefulr to use the underlying device name, like on other
>> platforms.
>
> It doesn’t look like macOS gives displays any sort of human readable
> name. The closest I can find is the monitor’s make and model, which
> appears to be lifted directly from the device driver. I expect if you
> have two identical monitors then it will be the same for both.
>

At least in 'system preferences/display', when you have two identical monitors
attached, they're called something like 'DELL 1234X' and 'DELL 1234X
(2)' (I canʼt test that right now). If you can show me code on how to
get those names in 10.14, I can confirm. That would be better than
making up names.

>> > Also, it might be worth considering using the ‘did’ value instead of
>> > ‘i’. As far as I can tell it’s just a uint32_t, and should stay the
>> > same as long as the system isn’t rebooted.
>> 
>> Is the did value reused if monitors are dynamically plugged and
>> unplugged ? This may happen when using a laptop with docking
>> stations and external monitors.
>
> The documentation implies it may remain the same for the same monitor,
> but then again, maybe not. It’s not very clear.
>
> It shouldn’t be the same for two different monitors, though.

I can respin to use the did, if thereʼs no better alternative.

Robert





  reply	other threads:[~2019-03-04  9:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 19:34 bug#34516: Multi-monitor frame sets Juri Linkov
2019-02-18 10:47 ` Robert Pluim
2019-02-18 21:03   ` Juri Linkov
2019-02-19  9:17     ` Robert Pluim
2019-02-23 20:43       ` Juri Linkov
2019-02-24 12:56         ` Robert Pluim
2019-02-24 21:08           ` Juri Linkov
2019-02-24 22:11             ` Andy Moreton
2019-02-25 21:11               ` Juri Linkov
2019-03-02 20:54           ` Alan Third
2019-03-02 23:57             ` Andy Moreton
2019-03-03 11:43               ` Alan Third
2019-03-04  9:52                 ` Robert Pluim [this message]
2019-03-04 13:56                   ` Andy Moreton
2019-03-04 16:10                     ` Robert Pluim
2019-03-04 19:20                       ` Alan Third
2019-03-04 20:18                         ` Robert Pluim
2019-03-19 21:33                           ` Juri Linkov
2019-03-26  7:24                             ` Robert Pluim
2019-03-26  7:26                               ` Robert Pluim
2019-03-27 21:46                                 ` Juri Linkov
2019-03-28  7:56                                   ` Robert Pluim
2019-03-28 21:57                                     ` Juri Linkov
2019-02-18 16:48 ` Eli Zaretskii
2019-02-18 21:16   ` Juri Linkov
2019-02-19  3:32     ` Eli Zaretskii
2019-02-19 21:37       ` Juri Linkov
2019-02-19 10:40     ` Andy Moreton
2019-02-19 21:31       ` Juri Linkov
2019-02-19 23:29         ` Andy Moreton
2019-02-20 21:20           ` Juri Linkov
2019-02-20 21:38             ` Andy Moreton
2019-02-23 20:48               ` Juri Linkov
2019-02-24  8:44                 ` martin rudalics
2019-02-24 21:08                   ` Juri Linkov
2019-02-24 22:13                   ` Andy Moreton
2019-02-25 10:13                     ` martin rudalics
2019-02-25 15:00                       ` Andy Moreton
2019-03-05  0:44 ` Andy Moreton
2019-03-29  8:16 ` Robert Pluim
2019-03-30 21:47   ` Juri Linkov
2019-04-01 11:29     ` Robert Pluim

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=m2ef7n2chi.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=34516@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=andrewjmoreton@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).