This would be great! I'm currently stuck on rwh 0.4 due to using an older version of wgpu.

This would be great! I'm currently stuck on rwh 0.4 due to using an older version of wgpu.

Thanks for the input, an extra data point to consider that maybe we should consider re-adding v0.4 support, in a deprecated form, and at least for a little while longer.

May I ask why you're stuck on the older wgpu?

Oh I thought this was already re-adding support but it looks like it is not!

FWIW it is not too much of a hassle for my case to add support in a fork.

May I ask why you're stuck on the older wgpu?

We currently depend on the dx11 backend to support users with older devices. Since the rewrite to use wgpu-hal, dx11 support is not fully rebuilt yet so we have been using the version of wgpu from before that. Wgpu now also has an Angle backend that can run on dx11 but we found a few things missing for our case the last time we tried it and going through Angle adds additional overhead that is not ideal on the older more resource constrained devices that we attempt to support via dx11.

let me know if you want me to do the Web implementation.

No thanks, I got it.

I would like some input on how we should do our examples, now that they require the rwh-0-5 feature to be enabled?

We could specify required-features = ["rwh-0-5"] for every example, but that means that users have to run with cargo run --example=my_example --features=rwh-0-5, which is a bit annoying. The other option is as I've hackily implemented, to stub out drawing to the window unless requested.

We could specify required-features = ["rwh-0-5"] for every example, but that means that users have to run with cargo run --example=my_example --features=rwh-0-5, which is a bit annoying.

[dev-dependencies]
winit = { path = "", default-features = false, features = ["rwh-0-5"] }

Is what I usually do. But that means you can't execute the examples without rwh-0-5, which might be fine?

EDIT:
Another example is to put a cfg in every example requiring either rwh-0-4 or rwh-0-5. We have done similar stuff in examples like x11_embed.

You could add recent raw window handle into the default feature set, which is what it should be, the previous versions should be enabled on demand.

You could add recent raw window handle into the default feature set, which is what it should be, the previous versions should be enabled on demand.

The problem is that the current version could easily change many times while the version of winit stays the same.

But I guess it'd be much more pragmatic.

@madsmtm feature set change is a breaking change. The default feature should be the one of the latest non-breaking release. it's not like you just specify raw-window-handle = "*".

I think this is all implemented now?