rzyns / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

Moving a fullscreen MacVim "space" from one monitor to another using Mission Control causes display issues #510

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
MacVim has a problem with handling the multi-monitor fullscreen mode added in 
OS X Mavericks. When open Mission Control and drag a MacVim "space" from one 
monitor to another monitor, MacVim doesn't realize that the size of the area it 
has to draw into has changed. The same thing happens if you have MacVim 
fullscreen on an external monitor and then unplug that monitor.

If the old monitor was smaller than the new monitor, MacVim will only occupy 
one corner of the screen. If the old monitor was larger, MacVim will draw 
itself too large and you won't be able to see the entire application.

The only fix is to leave fullscreen mode and then enter it again. Other 
applications handle this correctly, so it must be possible to do so. I imagine 
there's some event that MacVim isn't listening for, though that's just a guess.

What steps will reproduce the problem?
1. Make MacVim fullscreen on one monitor.
2. Open Mission Control and drag it to another monitor with a different size.

Alternate steps:
1. Make MacVim fullscreen on an external monitor with a different resolution 
than your laptop's built-in screen.
2. Unplug the external monitor.

What is the expected output? What do you see instead?

MacVim should resize itself to fit the new area. Instead, MacVim still thinks 
that it should draw at the size of the old monitor. Either part of the screen 
is empty, or part of MacVim is offscreen.

What version of MacVim and OS X are you using (see "MacVim->About MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6
Intel")?

Snapshot 72
OS X 10.9.4

Original issue reported on code.google.com by mark.set...@gmail.com on 8 Aug 2014 at 12:27

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I can confirm that this is still broken in Snapshot 73 under Yosemite (10.10.2).

Original comment by earl.oli...@gmail.com on 4 Feb 2015 at 7:48