Window.mouse_pos incorrect on 4k/retina displays
See original GitHub issueThe default Kivy window size is 800x600. However, when running on a high rez display (4k display, MacBookPro Retina Display), the default window size ends up 1600x1200. Fair enough. But, when querying Window.mouse_pos, the returned value appears as if the window size were 800x600.
For example, this:
def on_touch_down(self, touch):
print touch.pos
print Window.mouse_pos, '\n'
will print out:
(1438.0, 1068.0)
(719.0, 534.0)
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Mouse position wrongly processed on high-dpi screens? #4377
Hi, we experience a strange issue where the mouse pos seems to be wrongly ... Window.mouse_pos incorrect on 4k/retina displays #3960.
Read more >Mouse problems with display port 1.2 in M… - Apple Community
With macOS Sierra, there is strange thing with 4K display connected via DisplayPort in DP 1.2 MST mode (required for 60Hz refresh rate)....
Read more >Cursor position is wrong on mixed multi-monitor (retina with ...
Setup Multi-monitor system on Windows 10 or OSX with one "retina" display (on ... On Windows, the cursor is rendered at the wrong...
Read more >Let's fix this monitor positioning issue after many ... - Reddit
Sometimes the window is too large for 1080p and it will never resize to correct dpi because part of it is still on...
Read more >Issues with Anim Picker on Retina/High DPI Monitors - Bug
I don't have a 4k monitor to test here, but it's very possible this issue also occurs on retina monitors with windows as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was likely fixed as part of #4403
Just tested on ios with
and it appears to work as expected
I can also confirm that this has been fixed. Thanks
-Eran (iPhone)