unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Charles A. Roelli" <charles@aurox.ch>
Cc: 25818@debbugs.gnu.org
Subject: bug#25818: 25.2; frame moved off display does not return (OS X)
Date: Mon, 27 Feb 2017 09:05:14 +0100	[thread overview]
Message-ID: <58B3DDBA.6060003@gmx.at> (raw)
In-Reply-To: <m2lgssn3gy.fsf@aurox.ch>

 > No, I did not; thanks for the reminder.  In 24.3, with a second monitor
 > plugged in, (display-pixel-width) returns 1280, i.e. the width only of
 > my primary monitor.  In 24.4, in the same situation,
 > (display-pixel-width) returns 2330 = (+ 1280 1050).  Second monitor is
 > 1050 pixels wide.

So the problem occurs only with the second monitor plugged in?

 > In both the case of 24.3 and 24.4 with no external monitor attached,
 > (display-pixel-width) returns 1280.

And there is no problem in this case with 24.4?

 > So it seems that the code for `display-pixel-width' (or code that it
 > calls) was changed between those releases, maybe to support multiple
 > monitors.

The code was changed in two tranches

2013-05-20  YAMAMOTO Mitsuharu  <mituharu@math.s.chiba-u.ac.jp>

2013-07-04  YAMAMOTO Mitsuharu  <mituharu@math.s.chiba-u.ac.jp>

I'll CC him - maybe he can help us solving this issue in a more general
way.

 > I notice now that when running the test form on 24.3, the created frame
 > never actually leaves the visible portion of the screen.  For example,
 > when the code calls (sleep-for 1) with the frame supposedly being
 > offscreen according to its frame parameters (right before step 2), the
 > frame is in reality maybe 50 pixels left of the screen's right edge.
 > This is with just one monitor.  When I run the example with two
 > monitors, the frame just spills into the second monitor but does not go
 > further (since 24.3 does not seem to give correct values for
 > `display-pixel-width' with multiple monitors).

Do you mean that the value is already wrong for the primary monitor or
that the value simply does not account for the second monitor?

 > So it seems like there used to be code in Emacs that prevented a frame
 > from programmatically leaving the screen area in OS X.  For example, in
 > 24.3, if I call (modify-frame-parameters nil '((left . 10000))), the
 > frame is put, as above, about 50 pixels left of the screen's right edge.

In any case we have to change ediff-wind.el in order to fix the issue at
hand.

martin





  reply	other threads:[~2017-02-27  8:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 20:04 bug#25818: 25.2; frame moved off display does not return (OS X) Charles A. Roelli
2017-02-23  8:49 ` martin rudalics
2017-02-26 11:26   ` Charles A. Roelli
2017-02-26 15:40     ` Charles A. Roelli
2017-02-26 16:45       ` martin rudalics
2017-02-26 19:42         ` Charles A. Roelli
2017-02-27  8:05           ` martin rudalics [this message]
2017-02-27 10:34             ` Charles A. Roelli
2017-02-27 20:47             ` Charles A. Roelli
2017-02-28 10:12               ` Charles A. Roelli
2017-02-28 13:20               ` Anders Lindgren
2017-02-28 15:05                 ` Charles A. Roelli
2017-02-28 20:35                   ` Anders Lindgren
2017-02-28 22:05                     ` Drew Adams
2017-03-01 10:48                       ` Anders Lindgren
2017-03-01 16:10                         ` Drew Adams
2017-03-19 19:38                     ` Charles A. Roelli
2017-03-27 18:22                       ` Anders Lindgren
2017-04-02 14:14                         ` Charles A. Roelli
2017-04-03  8:33                           ` Anders Lindgren
2017-04-08 20:40                             ` Charles A. Roelli
2017-04-09 19:13                               ` Anders Lindgren
2017-04-10 19:54                                 ` Charles A. Roelli
2017-04-11 18:35                                   ` Anders Lindgren
2017-04-27 19:14                                     ` Charles A. Roelli
2017-04-27 20:05                                       ` Alan Third
2017-04-28 17:33                                         ` Charles A. Roelli
2017-05-02 20:33                                           ` Alan Third
2017-05-05 18:30                                             ` Charles A. Roelli
2017-04-29 10:30                                       ` martin rudalics
2017-04-29 11:15                                         ` Charles A. Roelli
2017-04-29 14:51                                           ` Alan Third
2017-04-29 17:23                                           ` Anders Lindgren
2017-04-30  8:32                                           ` martin rudalics

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=58B3DDBA.6060003@gmx.at \
    --to=rudalics@gmx.at \
    --cc=25818@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    /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).