2da24089de
* Experiment with github actions * Only use stable for testing simplicity * Disable fail-fast * Never fail when rustup target add fails * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Update rust.yml * Split formatting check into separate job * Update and rename rust.yml to ci.yml * Attempt to add web support * Fix things * Fixings * The "I'm not familiar with YAML" update * The empty string update * Fix target interpolation * Add gcc-multilib on linux x86 * Update ci.yml * Update ci.yml * Update ci.yml * Update ci.yml * Update ci.yml * Update ci.yml * Use correct host on Windows GNU * Update ci.yml * Update ci.yml * in my defense it was like 2 AM when I wrote this * Update ci.yml * Update ci.yml * Update ci.yml * Update ci.yml * try caching * Update ci.yml * Update ci.yml * Update on * Update ci.yml * Update ci.yml * Remove travis and appveyor testing * Cache entire cargo folder * Make cargo cache key more appropriately named * Reduce key collisions * Make key work * Add publish workflow and path qualifiers * Remove -f in cargo install cargo-web * continue-on-error for cargo web * ping * Try to shorten matrix * attempt two * attempt three * attempt four * Use bash * web feature formatting * ping |
||
---|---|---|
.github | ||
examples | ||
src | ||
tests | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
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-alpha6"
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
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.canvas
to 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
.js
file generated by Rust after theModule
variable is created.