Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 733
    • Issues 733
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 203
    • Merge requests 203
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #18195

Closed
Open
Created May 03, 2021 by Paul Dickens@dickens.paul

Picker coordinates scaled wrongly on Mac (MacOS 11.2.3) with a Retina display when embedding in Qt

#17049 (closed) reported an issue on OSX 10.12 where the picker coordinates are off by a factor of 2, when using a Retina display. The behaviour only occured when embedded in Qt. A fix was implemented in !4201 (merged).

However, on MacOS 11.2.3 the picker coordinates are again off by a factor of 2 on a Retina display when embedded in Qt, but in the opposite direction to the behaviour reported in #17049 (closed) (i.e. the returned coordinates are twice what they should be; in the original issue they were half what they should be).

The issue is resolved if the changes in !4201 (merged) are reverted.

I suspect that changes in MacOS or Qt to better handle high DPI screens render the fix in !4201 (merged) unnecessary. However, reverting !4201 (merged) may have unintended consequences for other platforms (e.g. 4k displays on Windows).

Attached are the two example apps from #17049 (closed). vtk_bug.py does not have the issue, while vtk_bug_qt.py (embedded in Qt) does have the issue.

Tested using PyQt5 version 5.15.3 and VTK version 9.0.1.

vtk_bug_qt.py

vtk_bug.py

Assignee
Assign to
Time tracking