a3739d6bad
Just before starting to poll/wait on calloop(mio), check if there are already events pending in the internal buffer of our wayland event queue. If so, dispatch them and force an instant wakeup from the polling, in order to behave as if we were instantly woken up by incoming wayland events. When using OpenGL, mesa shares our wayland socket, and also reads from it, especially if vsync is enabled as it'll do blocking reads. When doing so, it may enqueue events in the internal buffer of our event queue. As the socket has been read, mio will thus not notify it to calloop as read, and thus calloop will not know it needs to dispatch. In some cases this can lead to some events being delivered much later than they should. Combined with key repetition this can actually cause some flooding of the event queue making this effect event worse. Fixes #1148 |
||
|---|---|---|
| .github | ||
| examples | ||
| src | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| appveyor.yml | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| FEATURES.md | ||
| HALL_OF_CHAMPIONS.md | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
winit - Cross-platform window creation and management in Rust
[dependencies]
winit = "0.20.0-alpha3"
Documentation
For features within the scope of winit, see FEATURES.md.
For features outside the scope of winit, see Missing features provided by other crates in the wiki.
Contact Us
Join us in any of these:
Usage
Winit is a window creation and management library. It can create windows and lets you handle events (for example: the window being resized, a key being pressed, a mouse movement, etc.) produced by window.
Winit is designed to be a low-level brick in a hierarchy of libraries. Consequently, in order to show something on the window you need to use the platform-specific getters provided by winit, or another library.
use winit::{
event::{Event, WindowEvent},
event_loop::{ControlFlow, EventLoop},
window::WindowBuilder,
};
fn main() {
let event_loop = EventLoop::new();
let window = WindowBuilder::new().build(&event_loop).unwrap();
event_loop.run(move |event, _, control_flow| {
match event {
Event::WindowEvent {
event: WindowEvent::CloseRequested,
window_id,
} if window_id == window.id() => *control_flow = ControlFlow::Exit,
_ => *control_flow = ControlFlow::Wait,
}
});
}
Winit is only officially supported on the latest stable version of the Rust compiler.
Cargo Features
Winit provides the following features, which can be enabled in your Cargo.toml file:
serde: Enables serialization/deserialization of certain types with Serde.
Platform-specific usage
Emscripten and WebAssembly
Building a binary will yield a .js file. In order to use it in an HTML file, you need to:
- Put a
<canvas id="my_id"></canvas>element somewhere. A canvas corresponds to a winit "window". - Write a Javascript code that creates a global variable named
Module. SetModule.canvasto the element of the<canvas>element (in the example you would retrieve it viadocument.getElementById("my_id")). More information here. - Make sure that you insert the
.jsfile generated by Rust after theModulevariable is created.