GNU bug report logs -
#16517
Emacs and display resolution change
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#16517: Emacs and display resolution change
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 16517 <at> debbugs.gnu.org.
--
16517: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16517
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
> From: Fabrice Popineau <fabrice.popineau <at> gmail.com>
> Date: Wed, 22 Jan 2014 08:32:31 +0100
>
> The current Emacs trunk does not seem to honour display resolution change
> under Windows.
> There is one case where it is annoying: when the frame is fullsized.
> I have a laptop. I run `emacs -Q' , then `M-x toggle-frame-fullscreen'.
> Next I connect an external display with a higher resolution.
> The frame displays undecorated, but with a size of the previous screen
> resolution.
> I need to call `M-x toggle-frame-fullscreen' twice to get back a fullsized
> frame.
>
> I think that for handling at least this case, the following patch could be
> applied:
No comments, so I applied your patch. Thanks.
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
Hi,
The current Emacs trunk does not seem to honour display resolution change
under Windows.
There is one case where it is annoying: when the frame is fullsized.
I have a laptop. I run `emacs -Q' , then `M-x toggle-frame-fullscreen'.
Next I connect an external display with a higher resolution.
The frame displays undecorated, but with a size of the previous screen
resolution.
I need to call `M-x toggle-frame-fullscreen' twice to get back a fullsized
frame.
I think that for handling at least this case, the following patch could be
applied:
=== modified file 'src/w32term.c'
--- src/w32term.c 2014-01-06 17:22:52 +0000
+++ src/w32term.c 2014-01-22 05:49:45 +0000
@@ -4841,6 +4844,7 @@
if (f)
{
dpyinfo->n_cbits = msg.msg.wParam;
+ x_check_fullscreen(f);
DebPrint (("display change: %d %d\n",
(short) LOWORD (msg.msg.lParam),
(short) HIWORD (msg.msg.lParam)));
However I'm not sure of any possibly harmful side effects.
One thing I have observed is that if you start with a normal frame, lower
the resolution to some point where the y resolution is less than the height
of the frame, then the frame will become height-maximized. So if you raise
the resolution again, it will stay height-maximized.
I'm fine with that, but I'm not sure what users would expect. Memorizing
the frame geometry so that it will be restored in case of several
resolution change maybe more complex.
Apologies if I missed obvious points or ways to handle that.
Regards,
Fabrice Popineau
[Message part 5 (text/html, inline)]
This bug report was last modified 11 years and 120 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.