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.

Sign up for GitHub

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

Jump to bottom

[Linux] Multiple monitors identified as a single one #64

Closed
tomaka opened this issue Nov 3, 2016 · 3 comments
Closed

[Linux] Multiple monitors identified as a single one #64

tomaka opened this issue Nov 3, 2016 · 3 comments
Assignees
@francesca64
Labels
B - bug Dang, that shouldn't have happened C - in progress Implementation is proceeding smoothly D - average Likely as difficult as most tasks here DS - x11 P - normal Great to have

Comments

@tomaka
Copy link
Contributor

tomaka commented Nov 3, 2016

Original: rust-windowing/glutin#678
@tomaka tomaka mentioned this issue Nov 3, 2016
Closed
@tomaka tomaka added the DS - x11 label Nov 3, 2016
jrmuizel pushed a commit to jrmuizel/winit that referenced this issue Mar 29, 2017
Auto merge of rust-windowing#64 - notriddle:servo, r=mbrubeck
9a39d9c 
Merge from glutin upstream

This will allow servo/servo#8641 to finally merge in.

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/glutin/64)
<!-- Reviewable:end -->
@jwilm jwilm mentioned this issue Oct 9, 2017
Closed
@jwilm
Copy link
Contributor

jwilm commented Oct 9, 2017

It looks like get_available_monitors should actually return a list as expect now. However, get_current_monitor doesn't work properly. The problem seems to be that the value it's using for current position is the position within the current monitor, rather than its absolute position within the X screen.

@elinorbgr elinorbgr mentioned this issue Oct 26, 2017
Closed
@francesca64 francesca64 added B - bug Dang, that shouldn't have happened H - help wanted Someone please save us C - needs investigation Issue must be confirmed and researched D - average Likely as difficult as most tasks here P - normal Great to have C - in progress Implementation is proceeding smoothly and removed H - help wanted Someone please save us C - needs investigation Issue must be confirmed and researched labels May 6, 2018
@francesca64 francesca64 self-assigned this May 12, 2018
@francesca64
Copy link
Member

francesca64 commented May 12, 2018 •
edited
Loading

The problem seems to be that the value it's using for current position is the position within the current monitor

I don't know what the specific problem was, but the get_current_monitor function looked super messy, so I rewrote the entire thing. It works now, so this will be resolved quite soon.

francesca64 added a commit to francesca64/winit that referenced this issue May 13, 2018
@francesca64
X11: Fix get_current_monitor
3905b91 
Fixes rust-windowing#64
@francesca64 francesca64 mentioned this issue May 13, 2018
Merged
@francesca64
Copy link
Member

Even sooner than I expected, in fact: #515

francesca64 added a commit to francesca64/winit that referenced this issue May 13, 2018
@francesca64
X11: Fix get_current_monitor
8593cf6 
Fixes rust-windowing#64
francesca64 added a commit that referenced this issue May 14, 2018
@francesca64
X11: Fix get_current_monitor (#515)
d86f53a 
* X11: Fix get_current_monitor

Fixes #64

* impl Debug for MonitorId on all platforms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@francesca64 francesca64

Labels
B - bug Dang, that shouldn't have happened C - in progress Implementation is proceeding smoothly D - average Likely as difficult as most tasks here DS - x11 P - normal Great to have
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tomaka @francesca64 @jwilm