Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A monitor scale changed was detected message blocks the window #14883

Closed
10 tasks
Iqigai opened this issue Mar 7, 2021 · 9 comments
Closed
10 tasks

A monitor scale changed was detected message blocks the window #14883

Iqigai opened this issue Mar 7, 2021 · 9 comments

Comments

@Iqigai
Copy link

Iqigai commented Mar 7, 2021

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

Using spyder on a Windows 10 laptop connected to a bigger monitor with an HDMI connection.
When I disconnect it, there is message window that appears with the message:
"A monitor scale changed was detected.
We recommend restarting spyder..."
The issue is that this window appears behind the main spyder window and so cannot be dismissed as it is a blocking window.
To dismiss it, you need to reconnect the monitor.
Second, the window suggests to "Enable auto high DPI Scaling" which I did but the behavior remains the same.

What steps reproduce the problem?

  1. Open spyder with a laptop connect with HDMI to a monitor
  2. Disconnect the laptop from the monitor
  3. The spyder window is moved to the latpop's screen but it is blocked as there's an erro message window behind the main window that cannot be dismissed

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

1- The error message should be in front of the main window
2- if we tick the preferences / General / Interface / Auto high DPI scaling, the error window should not even open

Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

  • Spyder version: 4.2.2, installed with the Windows installer
  • Python version: 3.9.2
  • Qt version:
  • PyQt version:
  • Operating System name/version: Windows 10

Dependencies

PASTE DEPENDENCIES HERE
@ccordoba12 ccordoba12 changed the title Blocking error window "A monitor scale changed was detected" message blocks the window Mar 7, 2021
@ccordoba12 ccordoba12 added this to the 4.x (missing) milestone Mar 7, 2021
@ccordoba12
Copy link
Member

ccordoba12 commented Mar 7, 2021

Hey @Iqigai, thanks for reporting. We'll try to fix this problem in a future release.

@dalthviz, I think this message annoys people a lot and we should give them the possibility to hide it forever. What do you think?

@dalthviz
Copy link
Member

dalthviz commented Mar 8, 2021

Sure 👍

@Iqigai
Copy link
Author

Iqigai commented Apr 24, 2021

Hi,
I upgraded to spyder 5.0.1 and the issue is still there. Was it corrected in an earlier version and then regressed?

@ccordoba12
Copy link
Member

Nop, that's why it's still open.

@jeremymatt
Copy link

@ccordoba12 @dalthviz adding some method of permanently disabling this message would be very welcome (or better yet, turn it off by default if auto high DPI scaling is enabled), as this message can lock the user out of Spyder if an auxiliary monitor is disconnected. This just happened to me and I was unable to use Spyder to present an example I'd set up until I reconnected my monitor. The steps that caused this are (although I can't seem to make the problem occur again, not sure why):

  1. Connect a monitor that has a different auto scale than the primary monitor and open Spyder on that monitor. If you have to move the Spyder window onto the second monitor, do not check the "hide during current session" box.
  2. Disconnect the second monitor. Spyder detects the change in scale and pops up the "A monitor scale change was detected" message. For me, Spyder tried to place the popup window on the second monitor that was just disconnected where I could not get to it to close it. With this popup window up, the main Spyder window is inaccessible.

@dalthviz
Copy link
Member

Hi @jeremymatt thanks for the feedback, indeed I think this popup window restricts more than it helps at the end so having a way to disable it from the start (either by checking the high DPI setting enabled or a specific setting) could be worthy. What do you think @ccordoba12 ?

@raphaelquast
Copy link

hey, just wanted to add something in here... I just stumbled upon this popup and on my side it looks like this:

image

The desired button is behind the "don't show again" checkmark, the window is not resizeable and you cannot simply close it (e.g. the "X" button is grayed out)...

So for me this popup was basically something like "let's try to click on that hidden button and hope it does what I'd expect it to do"

@dalthviz dalthviz modified the milestones: 4.x, v5.3.3 May 10, 2022
@dalthviz
Copy link
Member

Thank you for the feedback @raphaelquast ! That makes things even worse 😨 (although not totally sure why the dialog layout would mess up in that way) What Spyder version are you using? Also could you share the resolutions you were using when this happened? Thanks!

@ccordoba12 ccordoba12 modified the milestones: v5.3.3, v5.3.2 May 10, 2022
@raphaelquast
Copy link

@dalthviz I'm using spyder 5.3.0. Concerning the resolution, unfortunately I can't say at the moment (it was not my screen and it might take some time till I get back there)

@dalthviz dalthviz changed the title "A monitor scale changed was detected" message blocks the window A monitor scale changed was detected message blocks the window Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants