nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxw309aex2mrp0yhx5c34x5hxxmmd9uqsuamnwvaz7tmwdaejumr0dshszythwden5te0dehhxarj9ekxzmny9u0ljp2l how did you guys fix this is android family, you had a similar issue when testing the app

Reply to this note

Please Login to reply.

Discussion

Damus*

We are using egui so we have the ability per-frame to do whatever we want.

Was surprisingly hard to do. Had to use getWindowInsets and inset change notifications to get the size if the keyboard

Then anytime we render an input box and if its focused, then was save the rectangle during that frame.

If the focused input box rectangle intersects with the keyboard inset rect we get from android, then we animate and resize the screen and make a bunch of view modifications so that the side toolbar isn’t squished.

If the keyboard doesn’t intersect any focused input boxes then nothing happens, which makes sense.

I’m pretty happy with the end result.

Graci for the explanier jb

Its true ai didn’t really help much, because the platform integrations didn’t yet exist. I had to add them to android-activity and winit.

Fun to work on greenfield tech that has no training data. These clankers aren’t replacing us yet 😂

https://github.com/damus-io/android-activity/commit/092a83b747937a2890ac219617a4252c001842ea

https://github.com/damus-io/winit/commit/9e4ea9de75222d2523a20f18d3a0a108c573737d