Re: correct iphoneSafeAreaInsets in iPad simulator?

[Klaus major-k via use-livecode]

Hi Ralph,

> Am 30.11.2022 um 22:37 schrieb Ralph DiMola via use-livecode 
> :
> 
> I did not have any problems on iPad Pro (11-inch) (3rd generation) simulator
> using iphoneSafeAreaInsets(). One thing I did notice that when you change
> rotation the resizestack handler is not firing. However it does work as
> expected on the device. LC or simulator bug?

maybe a simulator thing...

> Other than that, I have nothing.

You have answered, which is something. :-)

> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
> Of Klaus major-k via use-livecode
> Sent: Wednesday, November 30, 2022 3:40 PM
> To: How to use LiveCode
> Cc: Klaus major-k
> Subject: correct iphoneSafeAreaInsets in iPad simulator?
> 
> Sorry, here the link that does not automatically compresses an downloads the
> two images
> <https://www.dropbox.com/sh/x4165mhvr61ldsg/AADEsPdI_rbtJHzCVOMF6woMa?dl=0>

If someone wants to test my stack in the simulator or a real device, here a 
stripped down (one card) version:
<https://www.dropbox.com/s/gmls3bfte96q7oi/resize_stack_on_mobile.livecode.zip?dl=0>
Everything is in the card script.


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: correct iphoneSafeAreaInsets in iPad simulator?

[Ralph DiMola via use-livecode]

I did not have any problems on iPad Pro (11-inch) (3rd generation) simulator
using iphoneSafeAreaInsets(). One thing I did notice that when you change
rotation the resizestack handler is not firing. However it does work as
expected on the device. LC or simulator bug?

Other than that, I have nothing.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Klaus major-k via use-livecode
Sent: Wednesday, November 30, 2022 3:40 PM
To: How to use LiveCode
Cc: Klaus major-k
Subject: correct iphoneSafeAreaInsets in iPad simulator?

Sorry, here the link that does not automatically compresses an downloads the
two images
<https://www.dropbox.com/sh/x4165mhvr61ldsg/AADEsPdI_rbtJHzCVOMF6woMa?dl=0>


--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: correct iphoneSafeAreaInsets in iPad simulator?

[Ralph DiMola via use-livecode]

Klaus,

I see what you mean.

I had my resizing SW using a table that I just kept adding to as new models
were released. I gave up on that after the iPhone 14 pro was released. I now
use iphoneSafeAreaInsets(). It seems to work OK.

I will do some testing of one of my apps on the iPad Pro (11-inch) (3rd
generation) simulator.

Film at 11

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Klaus major-k via use-livecode
Sent: Wednesday, November 30, 2022 2:04 PM
To: How to use LiveCode
Cc: Klaus major-k
Subject: Re: correct iphoneSafeAreaInsets in iPad simulator?

Additional info:
I resize the stack to proportionally to the devices screen dimensions.
And that works fine on all tested iPhone simulators.
These differences are only on these two iPad simualtors.

> Am 30.11.2022 um 19:59 schrieb Klaus major-k via use-livecode
:
> 
> Hi friends,
> 
> here two screenshots from my app in the Apple iPad simulator:
> <https://www.dropbox.com/sh/x4165mhvr61ldsg/AADEsPdI_rbtJHzCVOMF6woMa?
> dl=1>
> 
> Same app***, same scripting, same "resizestack" handler taking 
> iphoneSafeAreaInsets() into account and reposition objects accordingly.
> 
> ***Only difference is that I disabled the group of buttons in the middle
in one simulator.
> 
> Please notice the much larger area of empty space below the navigation 
> widget and above the text field at the top in the screenshot of the iPad
Pro (11-inch) (3rd generation).
> 
> Is this a bug, a feature or just some inconvenience of the simulator?
> 
> Any insight welcome, thank you!
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

correct iphoneSafeAreaInsets in iPad simulator?

[Klaus major-k via use-livecode]

Sorry, here the link that does not automatically compresses an downloads the 
two images



--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: correct iphoneSafeAreaInsets in iPad simulator?

[Klaus major-k via use-livecode]

Additional info:
I resize the stack to proportionally to the devices screen dimensions.
And that works fine on all tested iPhone simulators.
These differences are only on these two iPad simualtors.

> Am 30.11.2022 um 19:59 schrieb Klaus major-k via use-livecode 
> :
> 
> Hi friends,
> 
> here two screenshots from my app in the Apple iPad simulator:
> <https://www.dropbox.com/sh/x4165mhvr61ldsg/AADEsPdI_rbtJHzCVOMF6woMa?dl=1>
> 
> Same app***, same scripting, same "resizestack" handler taking 
> iphoneSafeAreaInsets()
> into account and reposition objects accordingly.
> 
> ***Only difference is that I disabled the group of buttons in the middle in 
> one simulator.
> 
> Please notice the much larger area of empty space below the navigation widget 
> and above 
> the text field at the top in the screenshot of the iPad Pro (11-inch) (3rd 
> generation).
> 
> Is this a bug, a feature or just some inconvenience of the simulator?
> 
> Any insight welcome, thank you!
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

correct iphoneSafeAreaInsets in iPad simulator?

[Klaus major-k via use-livecode]

Hi friends,

here two screenshots from my app in the Apple iPad simulator:
<https://www.dropbox.com/sh/x4165mhvr61ldsg/AADEsPdI_rbtJHzCVOMF6woMa?dl=1>

Same app***, same scripting, same "resizestack" handler taking 
iphoneSafeAreaInsets()
into account and reposition objects accordingly.

***Only difference is that I disabled the group of buttons in the middle in one 
simulator.

Please notice the much larger area of empty space below the navigation widget 
and above 
the text field at the top in the screenshot of the iPad Pro (11-inch) (3rd 
generation).

Is this a bug, a feature or just some inconvenience of the simulator?

Any insight welcome, thank you!


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[Klaus major-k via use-livecode]

Hi Jaques,

> Am 11.08.2022 um 20:13 schrieb J. Landman Gay via use-livecode 
> :
> 
> On 8/11/22 7:44 AM, Klaus major-k via use-livecode wrote:
>> FYI, iPhoneSafeAreaInsets() returns EMPTY on Android.
> 
> It looks like it's for iOS only, Android isn't listed in the dictionary 
> reference. You'll probably need to use the working screenrect on Android.

yes, I just wanted to see if it will throw an error on Android.
It doesn't. :-)

> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[J. Landman Gay via use-livecode]

On 8/11/22 7:44 AM, Klaus major-k via use-livecode wrote:

FYI, iPhoneSafeAreaInsets() returns EMPTY on Android.


It looks like it's for iOS only, Android isn't listed in the dictionary reference. You'll 
probably need to use the working screenrect on Android.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[J. Landman Gay via use-livecode]

Actually some Android phones have notches to imitate iPhones when Apple 
first introduced that. It wasn't very popular and most Android phones now 
use punch holes, but those also take up a bit of space, though not much.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 11, 2022 10:29:29 AM Bob Sneidar via use-livecode 
 wrote:


It seems to me, someone who has done zero mobile development, that this 
function has no meaning on an android, and should therefore return empty to 
avoid unanticipated runtime errors.


There should be however a function to get the screen rects of an android. 
Does the effective working screenrect do it for you?


I see that your goal is to try and avoid platform checks, but iOS and 
Android seem to be such diverse OS platforms that checks are unavoidable. 
There are a TON of commands and functions beginning with iPhone. I stopped 
counting at 30 and I wasn't half way through. If all of these functions are 
to equivalent values for the Android OS, we'd be waiting 5 years for the 
enhancements.


Just my ignorant 2¢

Bob S


On Aug 11, 2022, at 05:44 , Klaus major-k via use-livecode 
 wrote:


iPhoneSafeAreaInsets() returns EMPTY on Android


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[Klaus major-k via use-livecode]

Hi Bob,

> Am 11.08.2022 um 17:27 schrieb Bob Sneidar via use-livecode 
> :
> 
> It seems to me, someone who has done zero mobile development, that this 
> function has no meaning on an android, and should therefore return empty to 
> avoid unanticipated runtime errors. There should be however a function to get 
> the screen rects of an android. Does the effective working screenrect do it 
> for you? 

Sure, but that is not the problem.

> I see that your goal is to try and avoid platform checks,

Yep, that is the goal, lazy moi! :-)

> but iOS and Android seem to be such diverse OS platforms that checks are 
> unavoidable. There are a TON of commands and functions beginning with iPhone.

Yes, and I still naively think that the IDE should just ignore these, so "if 
the platform = "mobile..." would not be neccessary anymore. 8-)

> I stopped counting at 30 and I wasn't half way through. If all of these 
> functions are to equivalent values for the Android OS, we'd be waiting 5 
> years for the enhancements. 
> Just my ignorant 2¢
> 
> Bob S
> 
> iPhoneSafeAreaInsets() returns EMPTY on Android

Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[Bob Sneidar via use-livecode]

It seems to me, someone who has done zero mobile development, that this 
function has no meaning on an android, and should therefore return empty to 
avoid unanticipated runtime errors. 

There should be however a function to get the screen rects of an android. Does 
the effective working screenrect do it for you? 

I see that your goal is to try and avoid platform checks, but iOS and Android 
seem to be such diverse OS platforms that checks are unavoidable. There are a 
TON of commands and functions beginning with iPhone. I stopped counting at 30 
and I wasn't half way through. If all of these functions are to equivalent 
values for the Android OS, we'd be waiting 5 years for the enhancements. 

Just my ignorant 2¢

Bob S


> On Aug 11, 2022, at 05:44 , Klaus major-k via use-livecode 
>  wrote:
> 
> iPhoneSafeAreaInsets() returns EMPTY on Android

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[Klaus major-k via use-livecode]

Hi all,

> Am 11.08.2022 um 14:44 schrieb Klaus major-k via use-livecode 
> :
> Hi all,
>> Am 15.07.2022 um 13:14 schrieb Klaus major-k via use-livecode 
>> :
>> Hi friends,
>> quick question, cannot test it myself in the moment.
>> Will -> iPhoneSafeAreaInsets() 
>> a. work or 
>> b. throw an error when being used on Android?
>> If a. I presume it will return "the screenrect" without any "notches".
>> Does it?
>> If b. then I will to check "if the platform = "iphone"..."
>> Thanks for any quick answer!
> FYI, iPhoneSafeAreaInsets() returns EMPTY on Android.
> Will file an enhancement request that is will return at least the screenrect 
> on Android,
> so there is no need for a PLATFORM check. 

and done: <https://quality.livecode.com/show_bug.cgi?id=23872>


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhoneSafeAreaInsets() and Android

[Klaus major-k via use-livecode]

Hi all,

> Am 15.07.2022 um 13:14 schrieb Klaus major-k via use-livecode 
> :
> 
> Hi friends,
> 
> quick question, cannot test it myself in the moment.
> 
> Will -> iPhoneSafeAreaInsets() 
> a. work or 
> b. throw an error when being used on Android?
> 
> If a. I presume it will return "the screenrect" without any "notches".
> Does it?
> 
> If b. then I will to check "if the platform = "iphone"..."
> 
> Thanks for any quick answer!

FYI, iPhoneSafeAreaInsets() returns EMPTY on Android.
Will file an enhancement request that is will return at least the screenrect on 
Android,
so there is no need for a PLATFORM check. 

We already need too much of them. 8-)


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iPhoneSafeAreaInsets() and Android

[Klaus major-k via use-livecode]

Hi friends,

quick question, cannot test it myself in the moment.

Will -> iPhoneSafeAreaInsets() 
a. work or 
b. throw an error when being used on Android?

If a. I presume it will return "the screenrect" without any "notches".
Does it?

If b. then I will to check "if the platform = "iphone"..."

Thanks for any quick answer!


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iphoneSafeAreaInsets()

[scott--- via use-livecode]

Thanks Ralph and Sean. I see where my expectations were wrong.
—
Scott


> On Feb 23, 2022, at 1:06 PM, Pi Digital via use-livecode 
>  wrote:
> 
> Hi there Scott. 
> 
> https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
> Layout Guides and Safe Areas
> 
> That will explain the safe areas as defined by Apple and implemented in the 
> library. 
> 
> Sean Cole
> Pi Digital Productions Ltd
> 
> eMail Ts & Cs
> 
> 
>> On 23 Feb 2022, at 20:29, scott--- via use-livecode 
>>  wrote:
>> 
>> Hmm… I had never noticed that mobileOrientation() and 
>> mobileDeviceOrientation() are different functions [ it doesn’t help that the 
>> documentation for mobileOrientation() seems to mistakenly refer to 
>> mobileDeviceOrientation() ] but mobileOrientation() seems like it should, 
>> unlike mobileDeviceOrientation(),  always be able to determine which side 
>> the notch is on.
>> 
>> —
>> Scott
>> 
>> 
>>> On Feb 23, 2022, at 12:15 PM, scott--- via use-livecode 
>>>  wrote:
>>> 
>>> I was updating a library to use the new iphoneSafeAreaInsets() for retuning 
>>> the inset of the iPhoneX notch. I was surprised to see that it reports an 
>>> inset on both left and right sides when in landscape even though the notch 
>>> is only on one side. I would have expected an iPhone in landscape to report 
>>> an inset on the bottom (for the home indicator, which it does report) and 
>>> on whichever side the notch was actually on. While this can usually be 
>>> figured out with  mobileDeviceOrientation()  (though not always) it seems 
>>> like an extra step in addition to just being inaccurate about one side. Am 
>>> I missing something or should this be a bug?
>>> 
>>> --
>>> Scott Morrow
>>> 
>>> Elementary Software
>>> (Now with 20% less chalk dust!)
>>> web   https://elementarysoftware.com/
>>> email sc...@elementarysoftware.com
>>> booth1-360-734-4701
>>> --
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iphoneSafeAreaInsets()

[Pi Digital via use-livecode]

Hi there Scott. 

https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
Layout Guides and Safe Areas

That will explain the safe areas as defined by Apple and implemented in the 
library. 

Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 23 Feb 2022, at 20:29, scott--- via use-livecode 
>  wrote:
> 
> Hmm… I had never noticed that mobileOrientation() and 
> mobileDeviceOrientation() are different functions [ it doesn’t help that the 
> documentation for mobileOrientation() seems to mistakenly refer to 
> mobileDeviceOrientation() ] but mobileOrientation() seems like it should, 
> unlike mobileDeviceOrientation(),  always be able to determine which side the 
> notch is on.
> 
> —
> Scott
> 
> 
>> On Feb 23, 2022, at 12:15 PM, scott--- via use-livecode 
>>  wrote:
>> 
>> I was updating a library to use the new iphoneSafeAreaInsets() for retuning 
>> the inset of the iPhoneX notch. I was surprised to see that it reports an 
>> inset on both left and right sides when in landscape even though the notch 
>> is only on one side. I would have expected an iPhone in landscape to report 
>> an inset on the bottom (for the home indicator, which it does report) and on 
>> whichever side the notch was actually on. While this can usually be figured 
>> out with  mobileDeviceOrientation()  (though not always) it seems like an 
>> extra step in addition to just being inaccurate about one side. Am I missing 
>> something or should this be a bug?
>> 
>> --
>> Scott Morrow
>> 
>> Elementary Software
>> (Now with 20% less chalk dust!)
>> web   https://elementarysoftware.com/
>> email sc...@elementarysoftware.com
>> booth1-360-734-4701
>> --
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: iphoneSafeAreaInsets()

[Ralph DiMola via use-livecode]

The corners are curved so rectangular safe areas are:
1) portrait==> from the bottom of the notch to the top of the corners at
bottom full width of the screen.
2) Landscape there are 2 options:
   a) Notch on left ==> from the right of the notch on left to the full
right side of screen. The height from the bottom of the top right corner to
the top of the bottom right corner.
   OR
   b) Notch on left ==> from the right of the notch on left to the left of
both right corners and full height screen height.

   So in landscape it's either full screen height or full screen
width(except for the notch)


If the notch is on the right it's the same but reversed.

Now you can use the areas beyond the corners but the corners of your card
will be cut off by the rounded screen corners

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of scott--- via use-livecode
Sent: Wednesday, February 23, 2022 3:16 PM
To: How to use LiveCode
Cc: sc...@elementarysoftware.com
Subject: iphoneSafeAreaInsets() 

I was updating a library to use the new iphoneSafeAreaInsets() for retuning
the inset of the iPhoneX notch. I was surprised to see that it reports an
inset on both left and right sides when in landscape even though the notch
is only on one side. I would have expected an iPhone in landscape to report
an inset on the bottom (for the home indicator, which it does report) and on
whichever side the notch was actually on. While this can usually be figured
out with  mobileDeviceOrientation()  (though not always) it seems like an
extra step in addition to just being inaccurate about one side. Am I missing
something or should this be a bug?

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth1-360-734-4701
--








___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iphoneSafeAreaInsets()

[scott--- via use-livecode]

Hmm… I had never noticed that mobileOrientation() and mobileDeviceOrientation() 
are different functions [ it doesn’t help that the documentation for 
mobileOrientation() seems to mistakenly refer to mobileDeviceOrientation() ] 
but mobileOrientation() seems like it should, unlike mobileDeviceOrientation(), 
 always be able to determine which side the notch is on.

—
Scott


> On Feb 23, 2022, at 12:15 PM, scott--- via use-livecode 
>  wrote:
> 
> I was updating a library to use the new iphoneSafeAreaInsets() for retuning 
> the inset of the iPhoneX notch. I was surprised to see that it reports an 
> inset on both left and right sides when in landscape even though the notch is 
> only on one side. I would have expected an iPhone in landscape to report an 
> inset on the bottom (for the home indicator, which it does report) and on 
> whichever side the notch was actually on. While this can usually be figured 
> out with  mobileDeviceOrientation()  (though not always) it seems like an 
> extra step in addition to just being inaccurate about one side. Am I missing 
> something or should this be a bug?
> 
> --
> Scott Morrow
> 
> Elementary Software
> (Now with 20% less chalk dust!)
> web   https://elementarysoftware.com/
> email sc...@elementarysoftware.com
> booth1-360-734-4701
> --
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iphoneSafeAreaInsets()

[scott--- via use-livecode]

I was updating a library to use the new iphoneSafeAreaInsets() for retuning the 
inset of the iPhoneX notch. I was surprised to see that it reports an inset on 
both left and right sides when in landscape even though the notch is only on 
one side. I would have expected an iPhone in landscape to report an inset on 
the bottom (for the home indicator, which it does report) and on whichever side 
the notch was actually on. While this can usually be figured out with  
mobileDeviceOrientation()  (though not always) it seems like an extra step in 
addition to just being inaccurate about one side. Am I missing something or 
should this be a bug?

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth1-360-734-4701
--








___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode