LiveCode Forums.

Having seen the recent discussion on the Use-List about notches, and wondering what a NOTCH
was, I did some Ecosia-ing [ https://www.ecosia.org/ ] and found out that it is a way of extending
a mobile phone's screen size while keeping the microphone and/or camera on the front of the
thing.

Whether having 2 "horns" to one's screen is a vast improvement or not is a funny question; from
a personal point of view I think it is pants, as in

"Every time I bend over my pants crawl up the notch in my iPhone."

But, oddly enough, the mobile phone industry and fashion and so on are not going to listen
to my opinion so developers are going to have to live with notches for now at least.

I also went here: https://dribbble.com/shots/4643636-Andr ... tch-Mockup

which prove quite useful, although I mucked around with the original version for my own use:
- -
and a thought occurred to me . . . "What is all the Hoo-Har about?"

Surely ALL that the Notch really means is that the screen space (think resolution) has
increased by the depth of the notch, but has the notch sticking into that extra screen are.

AND, forbye, what would one use those 2, frankly silly, extra bits of screen space for?

Nothing, surely.

However, one will still have to take into account those extra bits
when worrying about scaling and rotating.

Extracting the screen BAR the notch from that image gives one 317 x 631 (or, probably 320 x 630).

Doing the same thing WITH the notch gives one 317 x 651 (320 x 650).

Now, while I realise that is just "Richmond fooling around with his computer" it does
give some sort of idea about the difference.

-

I'm not sure yet how iPhones handle this, but Android specs say that the status bar must extend to the full height of the notch. That means every phone will have a different sized status bar. By default your stack will be placed under the status bar, and the area to the sides of the notch will be black.

I don't know whether LC adjusts the value of the screenrect (or possibly the effective screenrect) to account for the change but I'd assume it has to. Of course, assumptions aren't reliable so I'm still waiting for the definitive word, which I may have to figure out myself via the Android emulator.

It would be nice to allow the area around the notch to show some color at least, and I need to see if setting a card backcolor will do that. To allow Android to draw into this area also requires a change in the manifest and I also don't know if LC supports that either.

Lots to figure out. The easiest way forward is to ignore the whole issue and just let Android reposition the display.

This problem is probably explained is 3 pictures:
- -
Superficial, rich, bubble-brain.
- -
Needlessly expensive Hotel in Paris (France, not Texas).
- -
Cheap, clean Bed-and-breakfast in Pomorie, Bulgaria

I'm always going to go for the third one. But, unfortunately, most people won't.