Zoxc

I had new screenshots in mind instead of further editing.

> I'm not really sure what changes to the screen shots you would like to see. I just wanted fresh new screenshots so they exactly match the actual application.

> Is that something you need to correct? Yeah, it looks like a GitHub image update broke it.

0% means no packets were lost. There's 2 digits of precision currently with packet loss present.

It does appear that v3 fixes the memory regression. I did also do a quick performance check of v2.2.2 (Before) and v3 (After) is slower. Is there a change regrading...

If you want to do a local build you'd need my [mimalloc branch of rustc](https://github.com/Zoxc/rust/tree/win-mimalloc-local). You need to enable mimalloc with a `bootstrap.toml` file: ``` [rust] codegen-units = 1 mimalloc...

v3 with (After) and without (Before) MIMALLOC_PURGE_DELAY=-1: BenchmarkBeforeAfterBeforeAfterBeforeAfterTimeTime%Physical MemoryPhysical Memory%Committed MemoryCommitted Memory%🟣 clap:check1.2034s1.2103s 0.58%147.77 MiB151.25 MiB💔 2.36%216.66 MiB220.73 MiB💔 1.88%🟣 hyper:check0.1999s0.2004s 0.29%78.94 MiB78.94 MiB 0.00%142.50 MiB142.50 MiB -0.00%🟣 regex:check0.6826s0.6806s -0.30%108.03...

Why does this not use `android-activity`'s methods to show/hide the keyboard? It will then start to deliver text events, even if it's from the rather limited `GameTextInput` API.

Still that seems like something that should be fixed with `android-activity`s `NativeActivity` handling?

This change does make some text input with the software keyboard possible with egui. Android seems to emulate physical keys when a proper IME connection is missing.