Vladyslav Batyrenko

Hi! Yeah, it's a known issue. It was a limitation on the `winit`'s end, but just about two weeks ago they merged a PR that's supposed to fix it: https://github.com/rust-windowing/winit/pull/2365...

Hi @freiksenet! Thanks for creating an issue. To be honest, I've never tried this, but I think I'd start looking into how to create a custom render pass and render...

Hi! Apologies for the late response. I saw that `EguiContext` has a method called `set_fonts` accepting `FontDefinitions`, which can be initialized with custom `.ttf` or `.otf` fonts. I've never used...

Hi! Thanks for filing an issue. Yeah, unfortunately, `bevy_egui` doesn't have a proper touch device support, as it doesn't react to [touch events](https://bevy-cheatbook.github.io/input/touch.html) at all. I'll be happy to accept...

I think it shouldn't be difficult. I believe the only system you'll need to look into is `process_input`. But since I've never worked with touch devices, I've no idea how...

Wow, nice! If web touch device support lands into `winit`, that will be great. Thank you for your work on this @ryo33. @71e6fd52 if anyone wants to make a PR...

Hi! No, it's not possible atm, but it's definitely a feature I'd like to see in `bevy_egui`. I think there are the following major puzzles missing in the plugin: -...

Hi! Thanks for the report. Unfortunately, I don't have a device to test those mobile browsers on. On Android's Google Chrome the page opens, but the touch device support is...

That's weird... So you're saying that you have other Bevy examples working. From the backtrace I can see this fails when constructing a window - in the code which I...

Hi @rezural! Thanks for the question. You're right, currently, the only way to do that is to pass Egui context to each system interested in the inputs and call `has_pointer_focus`...