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

High DPI scaling messes up placement of breakpoint red circles #4734

Closed
DStauffman opened this issue Jul 11, 2017 · 2 comments
Closed

High DPI scaling messes up placement of breakpoint red circles #4734

DStauffman opened this issue Jul 11, 2017 · 2 comments

Comments

@DStauffman
Copy link
Contributor

The breakpoint red circle is drawn between two lines instead of on the relevant line when high DPI scaling is on.

What steps will reproduce the problem?

  1. Use 4K or other high DPI monitor with scaling turned on (may be unnecessary, I don't have an old one to test right now?)
  2. In general preferences, check "Enable high DPI scaling"
  3. Restart Spyder to enable high DPI scaling
  4. Place a breakpoint in a file

What is the expected output? What do you see instead?
The red circle should be nicely centered on the line with the intended breakpoint. Instead the circle is drawn about half a line high and it is unclear which line it corresponds to. Further, trying to turn it off often accidentally leads to turning another one on, but offset from the line you intended.

The breakpoint shown below is intended to be on line 8 with the command "pass", but shows up between lines 7 and 8.
breakpoint

Note, that turning off the scaling fixes the alignment, but then you are stuck with really small icons and circles.
breakpoint2

Please provide any additional information below

Versions and main components

  • Spyder Version: 3.1.4.dev0
  • Python Version: 3.6.1
  • Qt Version: 5.8.0
  • PyQt Version: 5.8.1
  • Operating system: Windows 10

Dependencies

jedi >=0.9.0 : 0.10.0 (OK)
matplotlib >=1.0 : 2.0.0 (OK)
nbconvert >=4.0 : 5.1.1 (OK)
numpy >=1.7 : 1.11.3 (OK)
pandas >=0.13.1 : 0.19.2 (OK)
pep8 >=0.6 : 1.7.0 (OK)
pyflakes >=0.6.0 : 1.5.0 (OK)
pygments >=2.0 : 2.2.0 (OK)
pylint >=0.25 : 1.6.5 (OK)
qtconsole >=4.2.0: 4.2.1 (OK)
rope >=0.9.4 : 0.9.4-1 (OK)
sphinx >=0.6.6 : 1.5.2 (OK)
sympy >=0.7.3 : 1.0 (OK)

@DStauffman
Copy link
Contributor Author

As I'm looking at this more, I noticed that it also happens for things like the orange exclamation triangle for code analysis issues.

@ccordoba12
Copy link
Member

Thanks for reporting. We'll at this one after we release Spyder 3.2

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

2 participants