Fedor Logachev

Thanks for PR! Generally I am totally fine with miniquad having platform-specific features, nothing wrong with that, we already have one - instancing. It works slightly different tho, the prefered...

Generally, platform dependend texture formats would involve a lot of design work. Miniquad should be better on expressing capabilities, but its not yet there. We tried to do in the...

> hmm... What about an API like > > ```rust > pub struct PrivateConstruct(()); > pub enum TextureFormat { > RGB8, > RGBA8, > RGBA16(PrivateConstruct), > Depth, > Alpha, >...

related PR that I believe was not fully migrated to miniquad-0.4 https://github.com/not-fl3/miniquad/pull/275

Can confirm, that's a bug. In megaui non-utf8 input is filtered out, so the problem never occurred, however, it would be nice to support non-utf8 characters somehow.

> @not-fl3 do you mean "non-latin" with "non-utf8"? `character.is_ascii()` in `widgets/editbox.rs` :) You can provide a non-utf8 string though and break things, so the bug actually is reproducible even with...

First naive try did not really work out - non ascii input for editbox is still broken even with my attempt to fix it. Will try again later!

To be honest I would prefer window manager to do its job and place window accordingly, at least by default. Maybe add a flag in `conf.platform` to make this behavior...

I just believe that apps should not manage their window placement, its the job for window manager (or the entire os in case of windows/mac), so I would prefer anything...

I've seen this error before, but I never managed to reproduced in either an emulator or any android devices I own :(( It shows up with `samsung SM-G960U1` from google...