raw-window-handle icon indicating copy to clipboard operation
raw-window-handle copied to clipboard

A common windowing interoperability library for Rust

Results 24 raw-window-handle issues
Sort by recently updated
recently updated
newest added

There are some `DisplayHandle` and `WindowHandle` variants that are completely safe to construct. For instance: - Most `DisplayHandle`s are just indicators of the currently running display system and don't involve...

`XlibDisplayHandle.display` and `XcbDisplayHandle.connection` are nullable; should they be? Previously discussed in https://github.com/rust-windowing/raw-window-handle/pull/136.

Sometimes there may be a situation where you need to ask a library what windowing systems it could support before initializing a library like winit. For example if running wgpu...

Since there are multiple ways to render on the web, including inserting e.g. an `svg` into the page, it seems to me like it would be more generic to give...

`RawDisplayHandle` documents that (emphasis mine): > Not all windowing systems have a separate display handle **(or they haven’t been implemented yet)** and their variants contain empty structs. So... We should...

I just merged #134, which adds a new web handle type based on references to a `JsValue`. I opted to merge it now so we can migrate bikeshedding to a...

From [the Rust API guidelines](https://github.com/rust-windowing/raw-window-handle/issues/144): - [ ] Crate level docs are thorough and include examples ([C-CRATE-DOC]) - [ ] All items have a rustdoc example ([C-EXAMPLE]) - [ ]...

documentation
good first issue

I'm only really familiar with macOS and iOS, but on those platforms it would make sense to split the window and the view handles in two. That way, users could...

enhancement

This pull request introduces a new field to the DRM display handle to specify the connector id. Rationale: Without a connector, the file descriptor may point to a DRM device...