Matlab windows and figures not working properly if second monitor is on the left, but perfect if on the right. Bug?

Question

Carmine Varriale 2017-8-22

4
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/353613-matlab-windows-and-figures-not-working-properly-if-second-monitor-is-on-the-left-but-perfect-if-on

评论： Doug McMartin 2017-9-12

My secondary monitor is physically on the left on the main one, and my settings in Windows 7 resemble this scenario, of course. If I open a new figure window on this secondary monitor (by default, or simply by dragging the figure from the first monitor to the secondary one) it would not work properly anymore. It would not display its content, but the background of the monitor or the underlying windows contents, and maximizing it or manually resizing the window would result in similar behavior, or even worse.

If I drag the figure to the main monitor everything works perfect again. Also, if I place the monitor to the right (or even to the bottom) of the main one in the Windows settings, everything works perfect again.

The same happens for other MATLAB windows, not only figures, like Documentation or File Explorer. Any help?

6 个评论
显示 4更早的评论隐藏 4更早的评论

Curtis Schroeder 2017-9-7

编辑：Curtis Schroeder 2017-9-7

My project has encountered a similar problem. We last used our plot script on 8/15 and Windows Updates were applied 8/28. Prior to 8/15 I updated the Nvidia Quadro driver to 385.08. The PC is equipped with a Quadro M5000.

I've tried rebooting Windows 7 Pro 64-bit, but that didn't help. I've tried setting the NVIDIA Global Profile to the "Dassault Systems - CATIA compatible" profile, but that didn't help. I've tried setting Windows Aero mode (we normally run in Basic mode), but that didn't help. We have verified Matlab is using opengl hardware rendering, but also tried software rendering and that didn't help.

Our PC has a total of four HD displays and our plots are configured to display on one of the secondary displays. This is a serious problem for our project.

Installing Windows HotFix KB4039884 solved our problem.

Doug McMartin 2017-9-12