Markus Røyset

> I agree that this is something that we need, would the intention then be to move e.g. #1759 to a separate crate that depends on winit? I've had thoughts...

###### This is an indirect response to [this comment](https://github.com/rust-windowing/winit/pull/2141#issuecomment-1009243586) So this whole platform-specific callback thing has a major usability issue as-is: it's kind of annoying to share state between the...

> Have you had a chance to do any work on this lately? Not really, no, but IIRC, the "initializing accessibility inside `CreateWindowExW`" problem requires a separate callback. Perhaps something...

> The `HWND` can be obtained through the `WM_NCCREATE` and `WM_CREATE` messages, which are sent during the call to `CreateWindowExW` ~~Is there some paramter or struct field I've missed somehow?...

Wow! This is neat. I'll be sure to look closer at this when I can, but for now, I just have to note that I think your editor's autoformatting bungled...

`Cargo.toml` and `FEATURES.md` both still have what looks like unintentional formatting changes.

> The main problem appears to be that winit marks every key as "handled" regardless of what the application does with it. It seems like there's a need to expose...

I'm personally not entirely sold on softbuffer's current API, but I think the benefits of adding it to the examples (i.e. no more complaints about windows not showing up on...

> what is the status of this PR? Aside from the lack of an X11 maintainer, I suppose we're waiting on @t-sin to respond to your review and resolve the...

It looks like it's all `softbuffer`'s fault.