-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Overlapping controls with fast overlay switching #704
Comments
Doesn't happen on my phone for whatever reason. |
Works fine on my Android 14 (Samsung Galaxy S23+) and Android 10 (Huawei P30 Pro) too. Can you share what Android version / device model are you using @rusty-snake ? |
I can reproduce this behavior on my physical Android 15 (API 35) device and on the virtual Android 13 (API 33) machine. Both are running on the latest Commit 9b95231 (freshly build from |
OK, played with developer option. Removing the display cut-out moves from it to the right position (although a bit spacing at the top wouldn't be wrong). So it looks like it is positioned relative to the screen rather then relative to the rest of the app. I also noticed that on small hights (landscape or split screen), it overlaps the bottom buttons. |
Thanks, so I'd say it's definitely something very similar to streetcomplete#6030 ("usable" screen size vs physical screen size).
This is a side effect on most of the UI being compose now, but the quick-switch still using the "normal" Android views. At some point I'll switch everything to compose, but that's a lot of work (at least initially for learning compose) and not priority. |
I wonder if streetcomplete#6074 might've helped with that... We should see on the next release 🤷♂️ |
Still a problem in 60.1 |
screenshot
How to Reproduce
Expected Behavior
No overlapping
Does it happen in normal StreetComplete?
No fast overlay switching avaiable
Versions affected
SCEE 60.0
The text was updated successfully, but these errors were encountered: