Re: sysError values...

[Rick Harrison via use-livecode]

Hi Paul,

I have gone down that road before too.
Yes, sysError 13 is a permissions error.

Rick

> On Jan 29, 2019, at 8:16 PM, Paul Dupuis via use-livecode 
>  wrote:
> 
> So thanks for finding this. I was Googling things like "Livecode list of 
> system errors" or "LiveCode sysError value list" and so on. I was hoping or 
> thinking LiveCode might have a FAQ or some document on their website listing 
> them.
> 
> That said, I am not sure this page actually represents the values returned by 
> the sysError() function in LiveCode. First of all it list two different 
> errors with code "13":
> 
> dsIrqErr = 13, /*uninstalled interrupt error*/
> sdmPRAMInitErr = 13, /*Slot PRAM could not be initialized.*/
> 
> Neither errors make much sense in the context of where in the script this 
> error is occurring. The script is attempting to write a file and it is 
> failing. I am 99% certain this issue is a permission issue (no write access 
> to the folder). However, have the exact and correct error message 
> corresponding to the sysError() function returning a value of 13 would be 
> nice to help troubleshoot.
> 
> 
> 
> On 1/29/2019 7:18 PM, Bob Sneidar via use-livecode wrote:
>> dsIrqErr = 13, /*uninstalled interrupt error*/
>> 
>> http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/
>> 
>> I just googled it. Google is a search engine where you type in words into a 
>> field on a web page that have something to do with what you want to know and 
>> then the search engine
>> 
>> NVM. :-P
>> 
>> Bob S
>> 
>> 
>>> On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode 
>>>  wrote:
>>> 
>>> In general, where does one find the English equivalent of the number 
>>> returned by sysError for a given OS?
>>> 
>>> In this specific case, the OS is OSX and the value is 13.
>> 
>> ___
>> 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: The Notch

[J. Landman Gay via use-livecode]

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: sysError values...

[Mark Wieder via use-livecode]

On 1/29/19 7:10 PM, Richard Gaskin via use-livecode wrote:

I wish Apple well, but I'm finding myself feeling hopeful as a result of 
their sales/stock drop. The best years of their relations with 
developers were when they were hungry, in the mid-90s. Hunger is 
tonifying.  Maybe another six months of decline and they'll start 
remember that it's app devs who make a platform worth using.




Apple appears a bit unclear on the concept...from an AP story:

"Apple hoped to offset slowing demand for iPhones by raising the prices 
of its most important product..."


--
 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: sysError values...

[Richard Gaskin via use-livecode]

Paul Dupuis wrote:

> I was Googling things like "Livecode list of system errors" or
> "LiveCode sysError value list" and so on. I was hoping or thinking
> LiveCode might have a FAQ or some document on their website
> listing them.
>
> That said, I am not sure this page actually represents the values
> returned by the sysError() function in LiveCode. First of all it list
> two different errors with code "13"...

And now you've discovered by LiveCode doesn't attempt to document OS 
error codes: If the OS vendor themselves can't keep it straight, how 
could any third party? :)


I wish Apple well, but I'm finding myself feeling hopeful as a result of 
their sales/stock drop. The best years of their relations with 
developers were when they were hungry, in the mid-90s. Hunger is 
tonifying.  Maybe another six months of decline and they'll start 
remember that it's app devs who make a platform worth using.


--
 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

Re: iOS simulator issue - LC 9.0.2, Xcode 10.0

[Terry Judd via use-livecode]

Thanks Curry - seems to be working for now at least after a full restart.  
Command line tools were set to the right version but interestingly although the 
iOS12 simulator runs, it doesn't show up in the list of installed simulators in 
the components pane of the Xcode prefs window.

Terry...


On 30/1/19, 12:05 pm, "use-livecode on behalf of Curry Kenworthy via 
use-livecode"  wrote:


Terry:

 > can’t get the simulator to run - it launches OK but LC throws an
 > error part way through the test/build process.
 > Unable to start simulator

I've seen that! Can't remember which fix is for which error, but the 
handiest fix that I use most for Simulator is xCode's prefs: Command 
Line Tools version. Never leave home (or stay home and use Sim) without 
it. :)

Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.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

[Ralph DiMola via use-livecode]

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: sysError values...

[Paul Dupuis via use-livecode]

So thanks for finding this. I was Googling things like "Livecode list of 
system errors" or "LiveCode sysError value list" and so on. I was hoping 
or thinking LiveCode might have a FAQ or some document on their website 
listing them.


That said, I am not sure this page actually represents the values 
returned by the sysError() function in LiveCode. First of all it list 
two different errors with code "13":


dsIrqErr = 13, /*uninstalled interrupt error*/
sdmPRAMInitErr = 13, /*Slot PRAM could not be initialized.*/

Neither errors make much sense in the context of where in the script 
this error is occurring. The script is attempting to write a file and it 
is failing. I am 99% certain this issue is a permission issue (no write 
access to the folder). However, have the exact and correct error message 
corresponding to the sysError() function returning a value of 13 would 
be nice to help troubleshoot.




On 1/29/2019 7:18 PM, Bob Sneidar via use-livecode wrote:

dsIrqErr = 13, /*uninstalled interrupt error*/

http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/

I just googled it. Google is a search engine where you type in words into a 
field on a web page that have something to do with what you want to know and 
then the search engine

NVM. :-P

Bob S



On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode 
 wrote:

In general, where does one find the English equivalent of the number returned 
by sysError for a given OS?

In this specific case, the OS is OSX and the value is 13.


___
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: iOS simulator issue - LC 9.0.2, Xcode 10.0

[Curry Kenworthy via use-livecode]

Terry:

> can’t get the simulator to run - it launches OK but LC throws an
> error part way through the test/build process.
> Unable to start simulator

I've seen that! Can't remember which fix is for which error, but the 
handiest fix that I use most for Simulator is xCode's prefs: Command 
Line Tools version. Never leave home (or stay home and use Sim) without 
it. :)


Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.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: sysError values...

[Bob Sneidar via use-livecode]

dsIrqErr = 13, /*uninstalled interrupt error*/

http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/

I just googled it. Google is a search engine where you type in words into a 
field on a web page that have something to do with what you want to know and 
then the search engine

NVM. :-P

Bob S


> On Jan 29, 2019, at 16:03 , Paul Dupuis via use-livecode 
>  wrote:
> 
> In general, where does one find the English equivalent of the number returned 
> by sysError for a given OS?
> 
> In this specific case, the OS is OSX and the value is 13.


___
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

iOS simulator issue - LC 9.0.2, Xcode 10.0

[Terry Judd via use-livecode]

I’m running LC 9.0.2 on OSX Mojave and can’t get the simulator to run - it 
launches OK but LC throws an error part way through the test/build process.

Unable to start simulator: 634,0,0,unknown
C++ exception
573,228,1,revIPhoneSetSimulatorSDK

Any ideas?
Building direct to a phone works fine BTW.

Terry…
___
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

[Bob Sneidar via use-livecode]

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

sysError values...

[Paul Dupuis via use-livecode]

In general, where does one find the English equivalent of the number 
returned by sysError for a given OS?


In this specific case, the OS is OSX and the value is 13.

___
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 via use-livecode]

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

[J. Landman Gay via use-livecode]

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

[Ralph DiMola via use-livecode]

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

[Mark Wieder via use-livecode]

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

[Bob Sneidar via use-livecode]

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

[Richard Gaskin via use-livecode]

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

[J. Landman Gay via use-livecode]

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: browserDocumentLoadComplete fired twice Mobile

[hh via use-livecode]

> You could use "the target" do get the browser
> that is calling the handler...

.. and put the browserDocumentLoadComplete *only*
in the card's script (or the stack's script if the
widgets are on different cards).


___
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: browserDocumentLoadComplete fired twice Mobile

[hh via use-livecode]

You could use "the target" do get the browser
that is calling the handler.

___
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: IndyCam2_v100

[JJS via use-livecode]

the PLUS is there cause it has some extras, so you are able to put your 
free app on Apple's store


Op 28-1-2019 om 00:20 schreef David Bovill via use-livecode:

Would be great to have a better description so I can see what it looks
like, and what it does? For instance i don't need or want snapshot
functionality - and I'm scared to fork out $500 for Indy - blind as i've no
real idea what is in there.

After all i just spend $80 or thereabouts on Community Plus because the
description made me think I'd have some sort of access to the commercial
plugins - only to find that is not the case. Surely this is a bad idea -
shouldn't we get some time to see if we want to buy?

On Sun, 27 Jan 2019 at 22:09, hh via use-livecode <
use-livecode@lists.runrev.com> wrote:


This is now updated to v102 that removes a display bug on Windows
where I could not make two cams visible at the same time. So, if
you have two cameras attached then you see on MacOS the display
of both and on Windows10 only the selected one.

Tested to work on MacOS 10.14 and Windows 10 with LC 9.0.2 Indy.


hh wrote:
*** The stack does NOT run with LC Community ***
(Because it uses the cameraControl that is available in
the Indy or Business versions of LC only.)

Download IndyCam2 from "Sample stacks" or
http://livecodeshare.runrev.com/stack/927/

You can take snapshots with up to two (intern oder extern)
cameras, may be also simple webcams.
Each snapshot has at about 240 KByte.

The snapshots can be filtered (directly in the stack) with
one of the image effects from LCImageToolBox_89.

There is also a timer for using this as timelapseCamera,
shooting in intervals of 1 to 36600 seconds. While such a
timelapse is running you can change the camera, the image
filter and the interval.

There is help in the stack.


___
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

Android needs 64 bit builds

[JJS via use-livecode]

Hi,


just to let you know, but probably if you have a dev account at google 
you've received this message too, so for people who don't have a dev 
account at google.


This was in the email from Google for Android builds.


Get your apps ready for the 64-bit requirement Starting August 1, 2019,

all new apps and app updates that include native code are required to 
provide 64-bit versions,


in addition to 32-bit versions, when publishing to Google Play.

We want to help you get ready and know you need time to plan.

So i'm looking forward to lc9dp1.


Cheers, Jerry


___
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

Google API places autocomplete

[Jose Enrique Montero via use-livecode]

Hi, wich could be the best way to use the autocomplete address from google
api places, on mobile app.

- Browser with javascript
-mobilecontrol field text + api post
- map widget

best regards
Jose
___
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

browserDocumentLoadComplete fired twice Mobile

[Sannyasin Brahmanathaswami via use-livecode]

browserDocumentLoadComplete

is not in the dictionary. It's in described in API doc for the browser widget. 
Maybe that is intentional

At any rate, for some reason if you have two browses widgets on the same card, 
but you have this in the script of only 1 browser widget 
 
widget "loader"
widget "Body"  # has the script:

On browserDocumentLoadComplete pURL
# so do stuff
End browserDocumentLoadComplete

On desktop, it fires once, as expected. 

But using Network Tracer (a God Sent Plugin!) on mobile it fires twice and I 
can see that it is fired once when "loader" in invoked and once again when 
"body" in loader.

If as if the widget "loader" has the script also, but it does not.

Can anyone confirm this?  if so I will report a bug. But it a nuisance really 
because I'm getting double entries in the "Journal"

Now if there is no way to determine from

 browserDocumentLoadComplete 

which browser is calling the handler, I would provide a conditional (pseudo 
code)

if the browser widget is "Loader" then 
# do nothing
  Else
 the browser widget is "body" 
setAddJournal pURL
end if

maybe a second parameter is needed

browserDocumentLoadComplete pURL pTarget



___
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: Script Editor Performance

[Mark Wieder via use-livecode]

On 1/29/19 8:43 AM, Bob Sneidar via use-livecode wrote:

Others have seen it and it seemed to be related to really long scripts.


I've seen it on 20-line scripts. With 9.0.2.

--
 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: Script Editor Performance

[Bob Sneidar via use-livecode]

I just did and am not seeing the issue. 9.0.2 Community MacOS 10.14.2

Bob S


> On Jan 29, 2019, at 08:43 , Bob Sneidar via use-livecode 
>  wrote:
> 
> Others have seen it and it seemed to be related to really long scripts. I am 
> running 9.0.2 and have not seen this for a while. Open the datagrid behavior 
> and scroll to the bottom. That should do it if it's gonna trigger. 
> 
> Bob S
> 
> 
>> On Jan 29, 2019, at 08:09 , Matthias Rebbe via use-livecode 
>>  wrote:
>> 
>>> Thanks for mentioning that.  I've seen that too, but only intermittently 
>>> and I haven't yet come up with a recipe.  Since no one else had mentioned 
>>> it I was beginning the think I was the only one seeing it.
>> 
>> As i wrote already in a post to a similar topic, i mostly can see this 
>> behaviour here on Mac OS X when in debug mode. When i then scroll, the line 
>> number very often do not update anymore, even if i jump into the next 
>> statement (CMD-i).
>> I then have to stop the script, close the script editor. After that it is 
>> working again until it happens again.


___
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: Script Editor Performance

[Bob Sneidar via use-livecode]

Others have seen it and it seemed to be related to really long scripts. I am 
running 9.0.2 and have not seen this for a while. Open the datagrid behavior 
and scroll to the bottom. That should do it if it's gonna trigger. 

Bob S


> On Jan 29, 2019, at 08:09 , Matthias Rebbe via use-livecode 
>  wrote:
> 
>> Thanks for mentioning that.  I've seen that too, but only intermittently and 
>> I haven't yet come up with a recipe.  Since no one else had mentioned it I 
>> was beginning the think I was the only one seeing it.
> 
> As i wrote already in a post to a similar topic, i mostly can see this 
> behaviour here on Mac OS X when in debug mode. When i then scroll, the line 
> number very often do not update anymore, even if i jump into the next 
> statement (CMD-i).
> I then have to stop the script, close the script editor. After that it is 
> working again until it happens again.


___
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: Script Editor Performance

[Matthias Rebbe via use-livecode]

Matthias Rebbe

free tools for Livecoders:
https://instamaker.dermattes.de 
https://winsignhelper.dermattes.de 

> Am 29.01.2019 um 16:14 schrieb Richard Gaskin via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> Tiemo Hollmann wrote:
> 
> > Beside of massive slowdowns, the 9er IDE has (at least on Win 10) some
> > nasty behaviors. E.g. When using the scroll-bar, the line numbers
> > don't get updated anymore. You have to stop scrolling and click
> > somewhere within the script to update the line numbers.
> 
> Thanks for mentioning that.  I've seen that too, but only intermittently and 
> I haven't yet come up with a recipe.  Since no one else had mentioned it I 
> was beginning the think I was the only one seeing it.

As i wrote already in a post to a similar topic, i mostly can see this 
behaviour here on Mac OS X when in debug mode. When i then scroll, the line 
number very often do not update anymore, even if i jump into the next statement 
(CMD-i).
I then have to stop the script, close the script editor. After that it is 
working again until it happens again.


___
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: AW: Script Editor Performance

[Richard Gaskin via use-livecode]

Tiemo Hollmann wrote:

> Beside of massive slowdowns, the 9er IDE has (at least on Win 10) some
> nasty behaviors. E.g. When using the scroll-bar, the line numbers
> don't get updated anymore. You have to stop scrolling and click
> somewhere within the script to update the line numbers.

Thanks for mentioning that.  I've seen that too, but only intermittently 
and I haven't yet come up with a recipe.  Since no one else had 
mentioned it I was beginning the think I was the only one seeing it.


Maybe it is time to write a new SE.  The line number thing nudged me in 
that direction.  Once we turn off all the features that distinguish LC's 
SE, it's a text field with an Apply button, rather like MC's.  Nothing 
fancy, but super quick and fluid to work with.


--
 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

AW: Script Editor Performance

[Tiemo Hollmann TB via use-livecode]

I am still trying to find reproducible recipes. Sometimes it really is a mess 
to work with the IDE, sometimes (same stack, same script) it is acceptable (not 
nice, not performant, but acceptable). I have switched off all "fancy features".

Beside of massive slowdowns, the 9er IDE has (at least on Win 10) some nasty 
behaviors. E.g. When using the scroll-bar, the line numbers don't get updated 
anymore. You have to stop scrolling and click somewhere within the script to 
update the line numbers.

From time to time when working with the script and switching back to the main 
stack window, the window is disappeared, it even doesn't show up anymore in the 
window menu, though the window still is "anywhere". After some more clicking, 
the main window appears again - very strange!

In total very dissatisfying
Still trying to find recipes, Tiemo


-Ursprüngliche Nachricht-
Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von 
Ray via use-livecode
Gesendet: Montag, 28. Januar 2019 22:58
An: use-livecode@lists.runrev.com
Cc: Ray 
Betreff: Re: Script Editor Performance

Thanks Curry - I'm using Windows 10.  I'll try some of these things you've 
suggested and get back.

On 1/28/2019 4:54 PM, Curry Kenworthy via use-livecode wrote:
>
> Ray:
>
> > For some time now I've noticed a substantial slowdown in the script 
> > editor every time I upgrade to 8.X or 9.X.
>
> If you're lucky, making adjustments (disabling real time protection 
> mode or whitelisting LC and its filetypes) to your Anti Virus (such as 
> Windows Defender) may alleviate the symptoms of this problem. That 
> works in most but not all cases. Also turn off most of the "auto"
> features such as coloring and autocomplete and real-time compile in 
> the script editor. See this bug:
>
> https://quality.livecode.com/show_bug.cgi?id=21604
>
> And if applicable, add your own CC and note!
>
> Notice the bug title is misleading, because (as I found out after 
> filing the report) Macs sometimes have the same symptoms. Which 
> platform are you using?
>
> If you're not lucky and tweaking (or changing) AV doesn't do the 
> trick, or if you're on Mac, please consider attempting a reliable 
> recipe, because that has proved elusive. At the moment I'm no longer 
> able to flip a setting on my computer to cause the Anti Virus obvious 
> exaggeration of the symptoms on Windows, but eventually when I have 
> some time I may attempt a recipe for Mac.
>
> > Which version of LC are you using?
>
> I'm one of the lucky ones with greatly reduced symptoms after changing 
> my AV, so using LC 902 an 901 on Win 10 and Mac, also LC 6.7 on Win 10 
> and Mac for some work.
>
> Best wishes,
>
> Curry Kenworthy
>
> Custom Software Development
> "Better Methods, Better Results"
> LiveCode Training and Consulting
> http://livecodeconsulting.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


___
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