How does Corona work with cutouts on the modern phones screen's?

Try this:

\<?xml version="1.0" encoding="utf-8"?\> \<resources\> \<color name="ic\_launcher\_background"\>#f4721e\</color\> \<style name="ActivityTheme"\> \<item name="android:windowLayoutInDisplayCutoutMode"\> shortEdges \<!-- default, shortEdges, never --\> \</item\> \</style\> \</resources\>

Tried Rob, but nothing to do. to set the app to full screen I have to force it from the phone settings.

The black bar remains in the compiled corona mode.

But in the build.setting beyond the maxaspect do I have to call something? Should the status bar be declared in any particular way?

thanks again for your help Rob

Good morning Rob,

Are there any news? but is the corona support working? to know what to say to the company

Best regards

I spoke with Engineering. There is some legacy building constraints blocking us from getting this support working. We are working on removing those constraints and then we can move forward with adding this.

Rob

Thanks Rob and thanks to all the corona team.

I look forward to this update to publish my app.

Best regards

Good evening Rob Do you have an estimate of the time to resolve the full screen on S10? my employer presses me :frowning:

Thanks

Best regards

No, we don’t have an ETA on this. 

Good morning,

Is there anything new in the management of coutout displays android?

Version Corona 2019.3563 ?

Android: added initialSystemUiVisibility property to ‘android’ key in build.settings (#32)

Thanks

Best regards

There are a couple of android fixes in the past couple of builds: 

added initialSystemUiVisibility property to ‘android’ key in build.settings (#32)

fixed System UI loosing its state

I don’t know if either of those two help, but it’s worth trying. I don’t know of any specific work we’ve done in recent builds to address the cutouts.

Rob

Hi Rob,

Sorry if I write here, but I wanted to know if there are news on the cutouts screen, I honestly see the whole world corona sdk very still with server problems and it worries me. I would not like to arrive and find myself displaced.

Can you give me some updates on the corona sdk in general?

do you continue the development work?

Best regards

Andrea

There isn’t any updates unfortunately.

Rob

Hi Rob, is there any news? How is the Corona situation?

Developments continue? months have passed and I no longer know what to say to my employer

Best regards

Well, it’s been just over a month, but more importantly, I think I can answer your question as well.

While this is an important feature, the current focus is in getting Corona to build offline (i.e. getting rid of the build servers). Then, as per Vlad’s post, the list of priorities following offline builds seem to be as follows: “Apple’s Metal (probably via MoltenVK), AndroidX and modern Windows”.

If I am not mistaken, this cutout issue should be addressed when AndroidX gets implemented. Now, I have no realistic time frames as to when that might happen , but it is safe to assume that it’ll take until May for the offline builds to kick in, then _maybe _another few months at least for Apple’s Metal to be implemented, after which work might begin on AndroidX.

Hi Rob, is there any news? How is the Corona situation?

Developments continue? months have passed and I no longer know what to say to my employer

Best regards

Well, it’s been just over a month, but more importantly, I think I can answer your question as well.

While this is an important feature, the current focus is in getting Corona to build offline (i.e. getting rid of the build servers). Then, as per Vlad’s post, the list of priorities following offline builds seem to be as follows: “Apple’s Metal (probably via MoltenVK), AndroidX and modern Windows”.

If I am not mistaken, this cutout issue should be addressed when AndroidX gets implemented. Now, I have no realistic time frames as to when that might happen , but it is safe to assume that it’ll take until May for the offline builds to kick in, then _maybe _another few months at least for Apple’s Metal to be implemented, after which work might begin on AndroidX.