Re: New MacBook Pro Display Notch
Hi I saw a MacRumors.com <http://macrumors.com/> article about this issue. https://www.macrumors.com/2021/10/28/scale-to-fit-below-built-in-camera-setting-notch/ <https://www.macrumors.com/2021/10/28/scale-to-fit-below-built-in-camera-setting-notch/> They gave another link to some recently released Apple documentation that explains to users how to enable the ‘Scale to fit below built-in camera’ mode that prevents your menu bar from being partially obscured by the notch. How to adjust an app's settings to appear below the camera area on your 14-inch or 16-inch MacBook Pro https://support.apple.com/en-us/HT212842 <https://support.apple.com/en-us/HT212842> This is something you can point your users who are encountering the problem. Martin > On Oct 19, 2021, at 4:06 PM, Mike Kerner via use-livecode > wrote: > > I'm not sure this will be a problem, unless you are trying to display > something in the menubar, since that's where the notch is going to be. > > On Tue, Oct 19, 2021 at 5:14 AM Richmond via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> I should have thought the simplest way round this problem was to work on >> the assumption that from now on >> ALL Apple displays will have a notch and "cut one's stack" to >> accommodate that. >> >> Of course this is only relevant to people who want to annoy end-users by >> providing full-screen window apps. >> >> On 19.10.21 11:55, HENRY LOWE via use-livecode wrote: >>> The new 14 and 16 inch MacBook Pro models announced by Apple yesterday >> include a display notch to house the 1080P front facing camera. Clearly >> this may cause problems for apps that display content in the screen area >> occupied by the new notch. >>> >>> In response Apple has created a new “compatibility mode” for apps >> running on Macs with a notch. When this mode is active, the system changes >> the active area of the display to avoid the camera housing. This mode can >> be turned on/off by the user via a checkbox in the app’s get info panel or >> it can be activated or deactivated by the developer via a new ‘info.plist’ >> key. >>> >>> Link to Apple developer documentation on how to turn on / off this mode >> using the new ‘info.plist’ key is below: >>> >>> >> https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode >>> >>> Henry >>> >>> Ascriva Health Informatics >>> ___ >>> 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 >> > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > ___ > 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: New MacBook Pro Display Notch
I'm not sure this will be a problem, unless you are trying to display something in the menubar, since that's where the notch is going to be. On Tue, Oct 19, 2021 at 5:14 AM Richmond via use-livecode < use-livecode@lists.runrev.com> wrote: > I should have thought the simplest way round this problem was to work on > the assumption that from now on > ALL Apple displays will have a notch and "cut one's stack" to > accommodate that. > > Of course this is only relevant to people who want to annoy end-users by > providing full-screen window apps. > > On 19.10.21 11:55, HENRY LOWE via use-livecode wrote: > > The new 14 and 16 inch MacBook Pro models announced by Apple yesterday > include a display notch to house the 1080P front facing camera. Clearly > this may cause problems for apps that display content in the screen area > occupied by the new notch. > > > > In response Apple has created a new “compatibility mode” for apps > running on Macs with a notch. When this mode is active, the system changes > the active area of the display to avoid the camera housing. This mode can > be turned on/off by the user via a checkbox in the app’s get info panel or > it can be activated or deactivated by the developer via a new ‘info.plist’ > key. > > > > Link to Apple developer documentation on how to turn on / off this mode > using the new ‘info.plist’ key is below: > > > > > https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode > > > > Henry > > > > Ascriva Health Informatics > > ___ > > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: New MacBook Pro Display Notch
I should have thought the simplest way round this problem was to work on the assumption that from now on ALL Apple displays will have a notch and "cut one's stack" to accommodate that. Of course this is only relevant to people who want to annoy end-users by providing full-screen window apps. On 19.10.21 11:55, HENRY LOWE via use-livecode wrote: The new 14 and 16 inch MacBook Pro models announced by Apple yesterday include a display notch to house the 1080P front facing camera. Clearly this may cause problems for apps that display content in the screen area occupied by the new notch. In response Apple has created a new “compatibility mode” for apps running on Macs with a notch. When this mode is active, the system changes the active area of the display to avoid the camera housing. This mode can be turned on/off by the user via a checkbox in the app’s get info panel or it can be activated or deactivated by the developer via a new ‘info.plist’ key. Link to Apple developer documentation on how to turn on / off this mode using the new ‘info.plist’ key is below: https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode Henry Ascriva Health Informatics ___ 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
New MacBook Pro Display Notch
The new 14 and 16 inch MacBook Pro models announced by Apple yesterday include a display notch to house the 1080P front facing camera. Clearly this may cause problems for apps that display content in the screen area occupied by the new notch. In response Apple has created a new “compatibility mode” for apps running on Macs with a notch. When this mode is active, the system changes the active area of the display to avoid the camera housing. This mode can be turned on/off by the user via a checkbox in the app’s get info panel or it can be activated or deactivated by the developer via a new ‘info.plist’ key. Link to Apple developer documentation on how to turn on / off this mode using the new ‘info.plist’ key is below: https://developer.apple.com/documentation/bundleresources/information_property_list/nsprefersdisplaysafeareacompatibilitymode Henry Ascriva Health Informatics ___ 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: that stupid notch
Hi Stephen This is a new one on me. What notch do you refer to? Can you perhaps link a screen grab to show us what you mean? High Sierra is no longer updated by Apple so I’m not sure how you contribute this issue to them. I look forward to your response All the best Sean Cole Pi Digital Prod Ltd > On 16 Nov 2019, at 19:12, Stephen Barncard via use-livecode > wrote: > > My apologies to my LC friends here, as I am posting a platform-specific > issue that is not related to Livecode, but for some reason the 'notch' has > appeared in my menubar (High Sierra). > > I have a two screen system but the 'notch' only appears on one screen. > This is the dumbest thing I've seen from Apple. > First of all it's useless > Second it's taking up space in my menu-bar > > I can't find a thing about it on the interwebs - and I'm a pretty good > researcher. > > So with heavy heart and bruised ego, I ask > > have any of you see this? > does anyone know how to remove it? > > sqb > -- > Stephen Barncard - Sebastopol Ca. USA - > mixstream.org > ___ > 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
that stupid notch
My apologies to my LC friends here, as I am posting a platform-specific issue that is not related to Livecode, but for some reason the 'notch' has appeared in my menubar (High Sierra). I have a two screen system but the 'notch' only appears on one screen. This is the dumbest thing I've seen from Apple. First of all it's useless Second it's taking up space in my menu-bar I can't find a thing about it on the interwebs - and I'm a pretty good researcher. So with heavy heart and bruised ego, I ask have any of you see this? does anyone know how to remove it? sqb -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___ 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: The Notch
Thanks, that sounds like what the default Android setup does too. So if I understand it right, the screenrect returns the available area of the screen below the notch, and I assume that fullscreenMode adapts to only that area as well. My current project won't be supporting a landscape layout so at least I don't need to worry about that. I'll eventually start looking at the simulators/emulators to make sure I've got it right, but you've given me a head start for now. We're still at the design phase. The notch is a silly hardware decision, and I can't fathom why Android manufacturers think they need to copy Apple's ugly design. And from what I read on the Android blogs, very few Android users like the notch either, and many are virulently against it. Headache indeed. On 1/29/19 7:40 PM, Ralph DiMola via use-livecode wrote: For iOS it returns the rect of the largest rectangle on the screen in any of 3 orientations (iPhone X does not allow portrait upside down). An iPhone X not only has the notch but rounded corners and the "swipe up home deal" area that's always at the bottom and must remain visible and unimpaired. Another wrinkle is "landscape and the iPhone X(all models)". There are two layout choices for a rectangular landscape app. This assumes you are already adding a margin on the notch and bottom(home swipe area) sides. #1) Use up to the top of the screen and add a margin on the non-notch side so the app is not in the "curve" of the corner. This is what GetCardRect() does. #2) Use all the way to the edge of the non-notch side and add a top margin so the app is not in the "curve" of the upper left or upper right corner(depending on landscape left or right). So you can choose 1 of 2 different aspect ratios for a landscape iPhone X LC App. < headache headache headache headache headache> GetCardRect() also has the option to return the rect that does/doesn't include the keyboard area if visible. -- 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: The Notch
For iOS it returns the rect of the largest rectangle on the screen in any of 3 orientations (iPhone X does not allow portrait upside down). An iPhone X not only has the notch but rounded corners and the "swipe up home deal" area that's always at the bottom and must remain visible and unimpaired. Another wrinkle is "landscape and the iPhone X(all models)". There are two layout choices for a rectangular landscape app. This assumes you are already adding a margin on the notch and bottom(home swipe area) sides. #1) Use up to the top of the screen and add a margin on the non-notch side so the app is not in the "curve" of the corner. This is what GetCardRect() does. #2) Use all the way to the edge of the non-notch side and add a top margin so the app is not in the "curve" of the upper left or upper right corner(depending on landscape left or right). So you can choose 1 of 2 different aspect ratios for a landscape iPhone X LC App. < headache headache headache headache headache> GetCardRect() also has the option to return the rect that does/doesn't include the keyboard area if visible. 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 J. Landman Gay via use-livecode Sent: Tuesday, January 29, 2019 6:35 PM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: The Notch While Richard's recommendation is appealing, I can't really ask my customers to follow through. ;) I guess what I need to know is: What does the screenrect return on a notched phone? How about the rect of the card? Is it different than the screenrect? Google says the default display, with no flags set, places the app window fully under the notch and blacks out the areas at the sides. How does this affect the card size? Does it get shorter? Or crop? Or scale to the smaller area as though the phone had a different aspect ratio, resulting in pillarboxing? Android has flags that allow the app to use the areas around the notch, but LC doesn't tell us where those are, or even that a notch exists. I'm not sure what iOS does. I'll have to fire up simulators and emulators I suppose, but I'm hoping to save a lot of testing time if someone has already gone through this. On 1/29/19 4:40 PM, Ralph DiMola via use-livecode wrote: > I have not yet addressed the Android notch. My LG v20 has an offset to > the right notch but it's reserved for the OS. For the iPhone I have a > function GetCardRect(). It returns a standard issue 4 item rect. I > don't use things like the "the top of this card...". As well as taking > in account for the keyboard it accounts for the iPhone notches. I select "show the status bar" > in the iOS standalone settings and GetCardRect() takes care of the > rest. You can even test in the IDE. I detect if the aspect ratio is an > iPhone with a notch and you can see what will happen on the X. This > was an easy implementation for me because I rolled my own device > independence control placement library long ago using GetCardRect() to deal with the keyboard. > This was long before the iPhoneX. When the X appeared on the scene I > just added a dozen or so lines of code in GetCardRect() to deal with > it. iOS was very predictable because of Apples strict human interface > guidelines. It's out in the field and working nicely. But the Android is another matter. > There are so many variants to deal with. I just don't know how we can > deal with the Android notch without an LC implementation of an OS API > hook or a new Android manifest "Notch" key to keep the app out of the notch(or both). > > 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 J. Landman Gay via use-livecode > Sent: Tuesday, January 29, 2019 4:30 PM > To: LiveCode Mailing List > Cc: J. Landman Gay > Subject: The Notch > > I don't have an Android or iPhone with a notch. How do we deal with > positioning for those? Anything I need to know? > -- 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 ___ 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: The Notch
Say what you will about Steve Jobs (most people do) but I do not think he would have allowed this notched design. Bob S > On Jan 29, 2019, at 15:42 , J. Landman Gay via use-livecode > wrote: > >> OK - granted I had to look up what a Notch is... I'm sure someone thought it >> was a good idea at the time. All right... not quite so sure. Probably more >> along the lines of "what can we do to make smartphones less usable? We've >> already got folks typing with their thumbs..." >> https://bgr.com/2018/03/29/android-notch-vs-iphone-x-app-user-experience/ >> This looks like it might help... >> https://proandroiddev.com/making-notch-friendly-apps-for-android-75776272be5c >> > > I'd already seen the second link. The first one is amusing in its own way. > Maybe some notchy person can tell me whether LC apps (in fullscreen mode) > take up the whole screen or if they instead get pushed down underneath the > eyesore. > > It's all Apple's fault, they started all this. > > -- > Jacqueline Landman Gay ___ 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: The Notch
On 1/29/19 3:59 PM, Mark Wieder via use-livecode wrote: On 1/29/19 1:37 PM, Richard Gaskin via use-livecode wrote: J. Landman Gay wrote: > I don't have an Android or iPhone with a notch. How do we deal with > positioning for those? Anything I need to know? Here's the recipe I followed: 1. Place the phone in a durable bag. 2. Hammer it for 15 minutes or until the frustration with arbitrary design distinctions passes. 3. Mail the device to the manufacturer with a note reading, "Design improvements". 4. Buy a phone from a vendor with more confidence than one who needs to frustrate their entire ecosystem with arbitrary design distinctions. ;) OK - granted I had to look up what a Notch is... I'm sure someone thought it was a good idea at the time. All right... not quite so sure. Probably more along the lines of "what can we do to make smartphones less usable? We've already got folks typing with their thumbs..." https://bgr.com/2018/03/29/android-notch-vs-iphone-x-app-user-experience/ This looks like it might help... https://proandroiddev.com/making-notch-friendly-apps-for-android-75776272be5c I'd already seen the second link. The first one is amusing in its own way. Maybe some notchy person can tell me whether LC apps (in fullscreen mode) take up the whole screen or if they instead get pushed down underneath the eyesore. It's all Apple's fault, they started all this. -- 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: The Notch
While Richard's recommendation is appealing, I can't really ask my customers to follow through. ;) I guess what I need to know is: What does the screenrect return on a notched phone? How about the rect of the card? Is it different than the screenrect? Google says the default display, with no flags set, places the app window fully under the notch and blacks out the areas at the sides. How does this affect the card size? Does it get shorter? Or crop? Or scale to the smaller area as though the phone had a different aspect ratio, resulting in pillarboxing? Android has flags that allow the app to use the areas around the notch, but LC doesn't tell us where those are, or even that a notch exists. I'm not sure what iOS does. I'll have to fire up simulators and emulators I suppose, but I'm hoping to save a lot of testing time if someone has already gone through this. On 1/29/19 4:40 PM, Ralph DiMola via use-livecode wrote: I have not yet addressed the Android notch. My LG v20 has an offset to the right notch but it's reserved for the OS. For the iPhone I have a function GetCardRect(). It returns a standard issue 4 item rect. I don't use things like the "the top of this card...". As well as taking in account for the keyboard it accounts for the iPhone notches. I select "show the status bar" in the iOS standalone settings and GetCardRect() takes care of the rest. You can even test in the IDE. I detect if the aspect ratio is an iPhone with a notch and you can see what will happen on the X. This was an easy implementation for me because I rolled my own device independence control placement library long ago using GetCardRect() to deal with the keyboard. This was long before the iPhoneX. When the X appeared on the scene I just added a dozen or so lines of code in GetCardRect() to deal with it. iOS was very predictable because of Apples strict human interface guidelines. It's out in the field and working nicely. But the Android is another matter. There are so many variants to deal with. I just don't know how we can deal with the Android notch without an LC implementation of an OS API hook or a new Android manifest "Notch" key to keep the app out of the notch(or both). 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 J. Landman Gay via use-livecode Sent: Tuesday, January 29, 2019 4:30 PM To: LiveCode Mailing List Cc: J. Landman Gay Subject: The Notch I don't have an Android or iPhone with a notch. How do we deal with positioning for those? Anything I need to know? -- 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: The Notch
I have not yet addressed the Android notch. My LG v20 has an offset to the right notch but it's reserved for the OS. For the iPhone I have a function GetCardRect(). It returns a standard issue 4 item rect. I don't use things like the "the top of this card...". As well as taking in account for the keyboard it accounts for the iPhone notches. I select "show the status bar" in the iOS standalone settings and GetCardRect() takes care of the rest. You can even test in the IDE. I detect if the aspect ratio is an iPhone with a notch and you can see what will happen on the X. This was an easy implementation for me because I rolled my own device independence control placement library long ago using GetCardRect() to deal with the keyboard. This was long before the iPhoneX. When the X appeared on the scene I just added a dozen or so lines of code in GetCardRect() to deal with it. iOS was very predictable because of Apples strict human interface guidelines. It's out in the field and working nicely. But the Android is another matter. There are so many variants to deal with. I just don't know how we can deal with the Android notch without an LC implementation of an OS API hook or a new Android manifest "Notch" key to keep the app out of the notch(or both). 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 J. Landman Gay via use-livecode Sent: Tuesday, January 29, 2019 4:30 PM To: LiveCode Mailing List Cc: J. Landman Gay Subject: The Notch I don't have an Android or iPhone with a notch. How do we deal with positioning for those? Anything I need to know? -- 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 ___ 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: The Notch
On 1/29/19 1:37 PM, Richard Gaskin via use-livecode wrote: J. Landman Gay wrote: > I don't have an Android or iPhone with a notch. How do we deal with > positioning for those? Anything I need to know? Here's the recipe I followed: 1. Place the phone in a durable bag. 2. Hammer it for 15 minutes or until the frustration with arbitrary design distinctions passes. 3. Mail the device to the manufacturer with a note reading, "Design improvements". 4. Buy a phone from a vendor with more confidence than one who needs to frustrate their entire ecosystem with arbitrary design distinctions. ;) OK - granted I had to look up what a Notch is... I'm sure someone thought it was a good idea at the time. All right... not quite so sure. Probably more along the lines of "what can we do to make smartphones less usable? We've already got folks typing with their thumbs..." https://bgr.com/2018/03/29/android-notch-vs-iphone-x-app-user-experience/ This looks like it might help... https://proandroiddev.com/making-notch-friendly-apps-for-android-75776272be5c -- Mark Wieder ahsoftw...@gmail.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: The Notch
They sent the phone back with a note that I had voided the warranty, for some reason. ;-) Bob S > On Jan 29, 2019, at 13:37 , Richard Gaskin via use-livecode > wrote: > > J. Landman Gay wrote: > > I don't have an Android or iPhone with a notch. How do we deal with > > positioning for those? Anything I need to know? > > Here's the recipe I followed: > > 1. Place the phone in a durable bag. > > 2. Hammer it for 15 minutes or until the frustration with arbitrary design > distinctions passes. > > 3. Mail the device to the manufacturer with a note reading, "Design > improvements". > > 4. Buy a phone from a vendor with more confidence than one who needs to > frustrate their entire ecosystem with arbitrary design distinctions. > > ;) > > -- > Richard Gaskin ___ 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: The Notch
J. Landman Gay wrote: > I don't have an Android or iPhone with a notch. How do we deal with > positioning for those? Anything I need to know? Here's the recipe I followed: 1. Place the phone in a durable bag. 2. Hammer it for 15 minutes or until the frustration with arbitrary design distinctions passes. 3. Mail the device to the manufacturer with a note reading, "Design improvements". 4. Buy a phone from a vendor with more confidence than one who needs to frustrate their entire ecosystem with arbitrary design distinctions. ;) -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.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
The Notch
I don't have an Android or iPhone with a notch. How do we deal with positioning for those? Anything I need to know? -- 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
