From: Ryan Prior <ryanprior@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 20619@debbugs.gnu.org, 21469@debbugs.gnu.org,
21348@debbugs.gnu.org, 18429@debbugs.gnu.org
Subject: bug#18429: bug#21469: bug#21348: 25.0.50; Screen scaling factor >=2 causes menus, tooltips to display in the wrong place
Date: Tue, 13 Oct 2015 11:34:34 -0500 [thread overview]
Message-ID: <CAHDL8oe--+4sZ4DnBQLDRf5u0KjJ7EugFbGDYY1RYZm0UkyxpA@mail.gmail.com> (raw)
In-Reply-To: <561D288E.7070803@gmx.at>
On Tue, Oct 13, 2015 at 10:51 AM, martin rudalics <rudalics@gmx.at> wrote:
> Are the frame parameters ‘top’ and ‘left’ affected? Suppose you do say
> (set-frame-parameter nil 'left 500) with scaling in effect. Does the
> frame appear 500 pixels left of the left screen edge? If not, then
> mouse warping (‘set-mouse-absolute-pixel-position’) is probably affected
> too and we really have to look into a more generic solution.
I spent some time playing with frame positions.
TABLE: `(set-frame-parameter nil 'left ,x)
_____________________________________________
x | actual frame distance from left screen edge (px)
0 | 20
500 | 520
1600 | 1620
1800 | 1772
2000 | 1772
A few observations:
1) offset of 20 pixels
I've never noticed this issue because it doesn't affect maximized
frames. Maybe that number 20 is significant somehow, or perhaps this
is a separate bug. The first time after I start `emacs -Q` and set the
left frame edge to 0, the frame flashes momentarily into place flush
with the left screen edge, for perhaps a single video frame, and then
jumps 20 pixels to the right. Subsequent calls to set the left frame
edge to 0 do not trigger this flashing behavior.
2) numbers are proportional, modulo the unexplained offset
We do not see doubling behavior here. I have added no scaling code
pertaining to frame positioning.
3) frame "sticks" to the right screen edge
Given the width of the frame I was testing with, when the left frame
edge is 1772 pixels from the left screen edge, the right frame edge is
flush with the right screen edge. Setting the left frame edge to a
greater value does not result in a further movement of the frame.
l appreciate any help with corroboration and analysis of these results.
Yours,
Ryan
next prev parent reply other threads:[~2015-10-13 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 22:51 bug#21348: 25.0.50; Screen scaling factor >=2 causes menus, tooltips to display in the wrong place Ryan Prior
2015-08-26 2:48 ` Eli Zaretskii
2015-08-26 8:56 ` martin rudalics
2015-08-26 15:33 ` Eli Zaretskii
2015-08-26 16:07 ` Glenn Morris
2015-08-27 7:58 ` martin rudalics
2015-08-26 8:56 ` martin rudalics
2015-10-12 21:10 ` bug#21469: " Ryan Prior
2015-10-13 15:51 ` bug#21348: " martin rudalics
2015-10-13 16:34 ` Ryan Prior [this message]
2015-10-13 17:21 ` bug#20619: " martin rudalics
2015-10-13 20:37 ` bug#21348: " Ryan Prior
2015-10-14 8:49 ` 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=CAHDL8oe--+4sZ4DnBQLDRf5u0KjJ7EugFbGDYY1RYZm0UkyxpA@mail.gmail.com \
--to=ryanprior@gmail.com \
--cc=18429@debbugs.gnu.org \
--cc=20619@debbugs.gnu.org \
--cc=21348@debbugs.gnu.org \
--cc=21469@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).