Hey bio1712! As I'm sort of lazy with programming, I tend to program a lot for some time and then just quit for a while. I had a new design idea and wanted to start programming. I thought I got the library and Love 11.3 safeArea working last time with your help, but it turns out it wasn't actually ...

"Uncomment to unhide status bar". I uncommented, and now the status bar is hidden... wtf... I was just going to play around with the themes in AndroidManifest, I got the status bar visible that way, but I couldn't edit it in any way.. I have no idea what's going on inside on these apps. T...

KallioSanteri wrote: ↑Mon Mar 02, 2020 2:20 pm I'd like to get the status bar transparent on top of the app, but I'll have to look into that a bit more. Cheers.

Try to open SDLActivity.java and edit lines 276-279.

I don't think LÖVE has ever done that, not even in 11.2 or previous. I think love.window.getSafeArea is intended mainly for fullscreen use, or maybe for more unusual cutouts in the screen, or other obstacles that are closer to the middle of the screen, that maybe get filled up even without fullscre...

I'm using the sample app ID, I don't have an Admob account yet. Isn't that black area on the left the area where the notch sits? Do you mean that the area should be filled even if the app is not in fullscreen mode? (Regardless of the banner) I think so, otherwise the function love.window.getSafeAre...

Hey! Thanks for the fast reply. Sure enough, it worked, thanks! I don't know how the 'smart' banner behaves with this modification, but the normal banner seems to work just fine (320x50). Only thing about the banner that is slightly off is that a black line sometimes appears on top of the banner an...

Hey! Thank you for the amazing library. However, I have faced an issue. The fullscreen mode doesn't seem to fill the area on the side of a notch. It basically only fills the "safe area". In the non-forked version of 11.3, it's possible to fill the whole screen even if there is a notch. Ha...

I've tried to use your development branch, however, even if I change LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES to LAYOUT_IN_DISPLAY_CUTOUT_MODE_NEVER, I still get the first image.
Therefore it is definitely a bug.

The issue is with SDLActivity which sets the flags View.SYSTEM_UI_FLAG_LAYOUT_STABLE and View.SYSTEM_UI_FLAG_VISIBLE as soon as the app stats in the method handleMessage(Message msg). It has nothing to do with the cutout mode, although I think the right one for us is LAYOUT_IN_DISPLAY_CUTOUT_MODE_SH...

Why do you think it's a problem with the buttons? Isn't it a problem with the notch?