Diggory Hardy

@OvermindDL1 it looks like it, given that a `PointerId` may be a `MouseId`, which is a platform-defined type (only the Windows variant is implemented here, and that's a unit type,...

Multi-mouse may not be exclusive to Linux either (though this sounds limited): https://www.mousemux.com/

Just tested [on X11](https://wiki.archlinux.org/index.php/Multi-pointer_X) + KDE: it works, but the second cursor causes horrible flickering. Additionally, it appears the keyboard *should* only follow the first pointer, but the second can...

Further note: the child windows created by this PR are limited to the area of their parent. In general, it can be useful to have child windows without this restriction...

> mostly since they don't support the same platforms as we do (glutin would be a better fit here) Will there ever be a perfect fit? Moreover, I'm skeptical that...

Quite aside from the use of softbuffer (which is now #2353), what is the status of this PR? - Winit has no X11 maintainer; nevertheless there isn't much code here...

Of course. I had hoped `softbuffer` would be a simple and reliable dependency, but clearly it is not.

Sounds good to me, though it would be worth considering how failures of `request_frame` should be handled (e.g. requesting a wake in 16ms?).

> I'm not sure I can justify this feature belonging to winit? It sounds like integration with regular desktop input facilities to me, given that the desktop platform is responsible...

Thanks for the quick response. I have no problem using `from_raw_os_error` in that case so I guess this is just a documentation issue.