-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add wayland support #30
Conversation
Ok, in a while I'll check the problem and upload a change |
Problem solved, for some reason I had put the |
@SergioRibera |
@nashaofu Yup, I didn't implement it because I couldn't find a way to get wayland to give me that information, if I find a way I'll do another PR. Although if you prefer I can make that the first element of the list is the primary one, I don't think that it applies in all the cases but it is what can be done for the moment |
Maybe the coordinates of the primary display is |
I think it would not apply in all cases, for example, my primary display is not at |
Get |
If you use the library from wayland it is very likely that you will not get good results, with this PR I intend to solve that problem, I am using smithay because it is the easiest way to work with wayland and as a first integration I think it is great.
Important
The only thing that could be a problem is the definition of the raw_handler because wayland doesn't really offer an option for this, I have manipulated this to create a handler, but I don't think it will work completely.
And also to know if the monitor is primary or not, I have not seen how to get that information, but I imagine it is possible.