Go to file
Murarth a70ac1531e
X11: Fix window creation hangs when another application is fullscreen (#1248)
* X11: Fix window creation hangs when another application is fullscreen

Previously, the X11 backend would block until a `VisibilityNotify` event
is received when creating a Window that is visible or when calling
`set_visible(true)` on a Window that is not currently visible. This
could cause winit to hang in situations where the WM does not quickly
send this event to the application, such as another window being
fullscreen at the time.

This behavior existed to prevent an X protocol error caused by setting
fullscreen state on an invisible window. This fix instead stores desired
fullscreen state when `set_fullscreen` is called (iff the window is not
visible or not yet visible) and issues X commands to set fullscreen
state when a `VisibilityNotify` event is received through the normal
processing of events in the event loop.

* Add window_debug example to facilitate testing

* Add a CHANGELOG entry

* Call `XUnmapWindow` if `VisibilityNotify` is received on an invisible window
2019-11-22 17:11:04 -07:00
.github Use paths for intra-doc links, and verify that links are valid in CI (#1244) 2019-11-11 16:05:59 -07:00
examples X11: Fix window creation hangs when another application is fullscreen (#1248) 2019-11-22 17:11:04 -07:00
src X11: Fix window creation hangs when another application is fullscreen (#1248) 2019-11-22 17:11:04 -07:00
tests Fix web errors (#1040) 2019-07-10 18:54:54 -04:00
.gitattributes Set CHANGELOG.md merge style to union (#919) 2019-06-13 16:11:44 -04:00
.gitignore TEMPORARY: add testing example 2019-06-17 22:54:07 -07:00
.gitmodules Forward porting (#966) 2019-06-23 02:39:26 -04:00
.travis.yml Use paths for intra-doc links, and verify that links are valid in CI (#1244) 2019-11-11 16:05:59 -07:00
appveyor.yml Use paths for intra-doc links, and verify that links are valid in CI (#1244) 2019-11-11 16:05:59 -07:00
Cargo.toml Release Alpha 4 (#1187) 2019-10-18 13:25:12 -04:00
CHANGELOG.md X11: Fix window creation hangs when another application is fullscreen (#1248) 2019-11-22 17:11:04 -07:00
CONTRIBUTING.md Move contributors table to wiki (#934) 2019-06-19 15:12:27 -04:00
FEATURES.md Update the feature matrix for wasm (#1218) 2019-10-09 19:49:12 -04:00
HALL_OF_CHAMPIONS.md Linkify HALL_OF_CHAMPIONS.md (#935) 2019-06-18 16:30:37 -06:00
LICENSE Initial commit 2014-07-27 11:41:26 +02:00
README.md Release Alpha 4 (#1187) 2019-10-18 13:25:12 -04:00
rustfmt.toml Re-format on stable rustfmt (#974) 2019-06-24 12:14:55 -04:00

winit - Cross-platform window creation and management in Rust

Crates.io Docs.rs Build Status Build status

[dependencies]
winit = "0.20.0-alpha4"

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:

Freenode Matrix Gitter

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. Set Module.canvas to the element of the <canvas> element (in the example you would retrieve it via document.getElementById("my_id")). More information here.
  • Make sure that you insert the .js file generated by Rust after the Module variable is created.