Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WASM Input (needs to be better) #246

Open
simbleau opened this issue Jan 8, 2024 · 2 comments
Open

WASM Input (needs to be better) #246

simbleau opened this issue Jan 8, 2024 · 2 comments

Comments

@simbleau
Copy link

simbleau commented Jan 8, 2024

This crate has a historic battle to handling input correctly on WASM. These problems make up a sizeable majority of unresolved issues:

As I understand it, bevy recently updated to winit 0.29 - which brought consistent APIs to physical keys vs. logical keys, right? (p.s. thanks @Vrixyz - bevyengine/bevy#10702)

Egui just released 0.25, which dually brought in changes to reflect the new winit 0.29 update.

I think we're now unblocked.

These are the issues I face daily working in a completely WASM codebase using bevy_egui and would love to see prioritized

@v-kat
Copy link
Contributor

v-kat commented Jan 17, 2024

Does #236 help with any of these issues? I was hoping the winit upgrade on bevy main would

@Vrixyz
Copy link
Contributor

Vrixyz commented Jan 22, 2024

Does #236 help with any of these issues? I was hoping the winit upgrade on bevy main would

Yes, alongside bevyengine/bevy#11400 ; I think we are able to drive #178 to completion 🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants