Skip to content
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

Rely on MaximizeUsingFullscreenGeometryHint flag to provide fullscreen experience on Android #5950

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nirvn
Copy link
Member

@nirvn nirvn commented Jan 20, 2025

This PR gets rid of our custom fullscreen handling on Android in favor of relying on the QML Window's MaximizeUsingFullscreenGeometryHint flag (like we already do on iOS).

On top lifting the burden of maintaining custom code by moving to Qt project code itself, using the flag provides a context that other parts of Qt may rely on to pick behavior based on the presence/absence of the flag (e.g. handlers).

if (dimension > 0) {
margin = dimension;
}
private Insets getSafeInsets() {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A note on this function: we'll be able to get rid of this one altogether when we move to Qt >= 6.9, where we finally have a safeAreaMargins implementation for Android (see https://bugreports.qt.io/browse/QTBUG-131519). We already use QPlatformWindow's safeAreaMargins on iOS and it'll be nice to use it for Android too.

That said, this is for a much latter date. Just stating for the record :)

@qfield-fairy
Copy link
Collaborator

qfield-fairy commented Jan 20, 2025

@nirvn nirvn force-pushed the android_fullscreen_upstream branch from 3224452 to 0984628 Compare January 20, 2025 10:39
@nirvn nirvn force-pushed the android_fullscreen_upstream branch from 0984628 to f2f9dbf Compare January 21, 2025 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants