5 commits

Author	SHA1	Message	Date
Joe Wilm	0b75a6b60c	Make keyboard input event order consistent ... All platforms should now receive events in the following order: 1. KeyboardInput(ElementState::Pressed, ..) 2. ReceivedCharacter 3. KeyboardInput(ElementState::Released, ..) cc https://github.com/tomaka/glutin/issues/878	2017-05-07 21:16:48 -07:00
Benjamin Saunders	22bc119cd7	Richer input events ... This expands input events to represent sub-pixel mouse positions, devices responsible for generating events, and raw device-oriented events. The X11 back end is refactored to make full use of the new expressiveness. Other backends have had new functionality minimally stubbed out, save for the macos backend which already supports sub-pixel mouse positions.	2017-04-23 01:08:15 -07:00
Victor Berger	9aaa788434	linux: Remove dead code from wayland & fix some trivial warnings.	2017-03-04 11:26:12 +01:00
Victor Berger	624a422f20	linux: move api transition boilerplate to x11/wayland submodules	2017-03-04 09:09:09 +01:00
Victor Berger	4acf437221	Move api module into platform::linux	2017-03-04 09:09:09 +01:00

Renamed from src/api/x11/mod.rs (Browse further)