Skip to content

Support for display-cutout #2766

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

Closed
wants to merge 4 commits into from
Closed

Support for display-cutout #2766

wants to merge 4 commits into from

Conversation

kuzeyron
Copy link
Contributor

@kuzeyron kuzeyron commented Mar 6, 2023

This PR enables the display-cutout functionality for python-for-android.

@kuzeyron
Copy link
Contributor Author

kuzeyron commented Mar 8, 2023

Still one problem. That's when full screen is set. Pre-compiled versions can be found here: display-cutout

@kuzeyron
Copy link
Contributor Author

Managed to clear out the problems with fullscreen.

@kuzeyron kuzeyron changed the title WIP -display-cutout Support for display-cutout Mar 11, 2023
@misl6
Copy link
Member

misl6 commented Mar 12, 2023

Hi @kuzeyron !

We now have a conflict, introduced by #2765 , can you please rebase and fix it?

@kuzeyron
Copy link
Contributor Author

Can you help me with the commands?

@kuzeyron
Copy link
Contributor Author

@misl6 Ping!

@misl6 misl6 self-assigned this May 4, 2023
Copy link
Member

@misl6 misl6 left a comment

Choose a reason for hiding this comment

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

Hi @kuzeyron,

Sorry for the late reply, but as you might know, we were pretty busy with the release process 😅

I've left some comments, let me know what do you think about it.

Comment on lines 75 to 76
``--display-cutout``: Enables the display cutout (notch) functionality.
`Android documentation <https://developer.android.com/develop/ui/views/layout/display-cutout>`__.
Copy link
Member

Choose a reason for hiding this comment

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

Hi @kuzeyron !

Maybe we can better explain that --display-cutout expects one of the supported display cutout methods as referenced in the Android documentation?

From the current explanation, it may look like that is a boolean flag.

Comment on lines 74 to 76
{% if support_cutout %}
android:theme="@style/BaseStyle"
{% endif %}
Copy link
Member

Choose a reason for hiding this comment

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

android:theme may be supported even if the device has no support for display-cutouts, and we will likely want to apply that feature to all the supported bootstraps.

Maybe, instead of @style/BaseStyle, we can rename it to @style/KivyManagedStyle ?

Comment on lines 549 to 550
"support_cutout": all([android_api >= 28,
args.display_cutout != 'never'])
Copy link
Member

Choose a reason for hiding this comment

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

Maybe support_cutout should only contain the feature availability, and instead the display_cutout != 'never' check should be done separately?

@kuzeyron
Copy link
Contributor Author

If anyone knows the way around @style please contact me.
Placing an empty style changes the look. Not when using default or shortEdges..

@kuzeyron kuzeyron closed this Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants