Skip to content

[macOS] ui.screens() returns incorrect coordinates on monitor disconnect / reconnect #278

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

Closed
ghost opened this issue Mar 31, 2021 · 1 comment
Milestone

Comments

@ghost
Copy link

ghost commented Mar 31, 2021

ui.screens() returns incorrect coordinates when I disconnect my external monitor and then when I reconnect it again. I have a 1440p external monitor (a Dell U2715H) and a MacBook Pro with a 1920x1200 display. I connect the monitor to my laptop with an HDMI cable through one of Apple's USB C multiport adapters.

Output before disconnecting:
[Screen(x=0.0, y=0.0, size=(2560.0, 1440.0), mm=(596.5504497563073, 335.5596279879229)), Screen(x=2560.0, y=746.0, size=(1920.0, 1200.0), mm=(330.63050350900426, 207.34693566147163))]

Output when I disconnect. I think this is wrong as x, y should be 0, 0:
[Screen(x=2560.0, y=746.0, size=(1920.0, 1200.0), mm=(330.63050350900426, 207.34693566147163))]

Output when I reconnect. Definitely wrong since it can't be that both displays have a 0,0 origin:
[Screen(x=0.0, y=0.0, size=(2560.0, 1440.0), mm=(596.5504497563073, 335.5596279879229)), Screen(x=0.0, y=0.0, size=(1920.0, 1200.0), mm=(330.63050350900426, 207.34693566147163))]

If I quit Talon completely and start it again, things are back to normal:
[Screen(x=0.0, y=0.0, size=(2560.0, 1440.0), mm=(596.5504497563073, 335.5596279879229)), Screen(x=2560.0, y=746.0, size=(1920.0, 1200.0), mm=(330.63050350900426, 207.34693566147163))]

Some more details:
Talon build 108-0.1.5-34-gc004
MacBook Pro (15-inch, 2018)
macOS Catalina (10.15.7)

@lunixbochs lunixbochs added this to the v0.2.0 milestone Apr 19, 2021
@lunixbochs lunixbochs mentioned this issue Sep 17, 2021
11 tasks
@lunixbochs
Copy link

this should be fixed in beta 0.2.0-85, please test and report any issues to the beta channel or #382

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

1 participant