Re: XCode 11 requirements

2019-12-05 Thread Matthias Rebbe via use-livecode
There is a Software-Update icon  in System Preferences, which should at least 
show up all available updates. There you can also setup if you want to search 
automatically for updates,  load them when available, automatically install 
them and so on. Maybe the option to automatically search for updates is not 
enabled.


Matthias Rebbe

free tools for Livecoders:
InstaMaker 
WinSignMaker Mac 

> Am 06.12.2019 um 06:17 schrieb J. Landman Gay via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> Thanks, I've downloaded the combo update to get me caught up. The odd thing 
> is that I never received any notifications that OS X updates were available, 
> and apparently I missed six of them. They weren't in the Mac App Store either 
> when I checked.
> 
> On 12/5/19 2:27 PM, Matthias Rebbe via use-livecode wrote:
>> If your Mac runs Mojave and is up to date then you should have 10.14.6 
>> already installed.
>> If you still have a lower Mojave version installed then you could find the 
>> updates for the 10.14.x among the updates for older and news os here
>> https://support.apple.com/downloads/macos 
>>  
>> > >
>> Btw the update from 10.14.2 to 10.14.3 can be found here 
>> https://support.apple.com/kb/DL1991?viewlocale=en_US&locale=en_US 
>>  
>> > >
>> Matthias Rebbe
>> free tools for Livecoders:
>> InstaMaker > >
>> WinSignMaker Mac > >
>>> Am 05.12.2019 um 20:35 schrieb J. Landman Gay via use-livecode 
>>> mailto:use-livecode@lists.runrev.com> 
>>> >> >>:
>>> 
>>> In LC 9.6 (dp 1) I get a warning that I can't use XCode 11 (which isn't 
>>> installed yet anyway) unless I update to Mac OS 10.14.3. My Mac is up to 
>>> date as far as I know and there is no OS 10.14.3 available in the Mac App 
>>> Store. I can't update to Catalina until some of my critical software 
>>> becomes compatible.
>>> 
>>> Is there a way to use XCode 10.1 in Mojave with LC 9.6?
>>> -- 
>>> 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
> 
> 
> -- 
> 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: XCode 11 requirements

2019-12-05 Thread J. Landman Gay via use-livecode
Thanks, I've downloaded the combo update to get me caught up. The odd 
thing is that I never received any notifications that OS X updates were 
available, and apparently I missed six of them. They weren't in the Mac 
App Store either when I checked.


On 12/5/19 2:27 PM, Matthias Rebbe via use-livecode wrote:

If your Mac runs Mojave and is up to date then you should have 10.14.6 already 
installed.
If you still have a lower Mojave version installed then you could find the 
updates for the 10.14.x among the updates for older and news os here

https://support.apple.com/downloads/macos 


Btw the update from 10.14.2 to 10.14.3 can be found here 
https://support.apple.com/kb/DL1991?viewlocale=en_US&locale=en_US 




Matthias Rebbe

free tools for Livecoders:
InstaMaker 
WinSignMaker Mac 


Am 05.12.2019 um 20:35 schrieb J. Landman Gay via use-livecode 
mailto:use-livecode@lists.runrev.com>>:

In LC 9.6 (dp 1) I get a warning that I can't use XCode 11 (which isn't 
installed yet anyway) unless I update to Mac OS 10.14.3. My Mac is up to date 
as far as I know and there is no OS 10.14.3 available in the Mac App Store. I 
can't update to Catalina until some of my critical software becomes compatible.

Is there a way to use XCode 10.1 in Mojave with LC 9.6?
--
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




--
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: Script Editor disassociates - a lossy LC IDE bug

2019-12-05 Thread Paul Dupuis via use-livecode

Windows 10 for me


On 12/5/2019 8:11 PM, Tom Glod via use-livecode wrote:

Are you all on Mac?  This does not ring a bell.

On Thu, Dec 5, 2019 at 8:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


On 12/5/2019 6:38 PM, Bob Sneidar via use-livecode wrote:

On Dec 5, 2019, at 15:04 , Paul Dupuis via use-livecode <

use-livecode@lists.runrev.com> wrote:

On 12/5/2019 5:42 PM, Curry Kenworthy via use-livecode wrote:

Wondering if this bug has already been reported?

I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window

seems to disassociate from the object being edited. Thus after this bug is
triggered, any typed script changes may not really be applied and saved,
although they are shown as applied. Next LC session, those changes are
gone; the stack code is still as it was prior to the bug being triggered
and prior to editing the script.

An alternate form is that the script changes actually are applied, but

in a bad way: first the script disassociates completely and is empty, then
the empty script is saved, overwriting the previous script. Nice! (I think
this is my favorite variation; if we're going to cause loss of work/code,
might as well do it boldly and not beat around the bush.)

I suspect this happens more on Mac than Windows, but since I don't

have a recipe, not sure. I've seen this happen to other people rather than
on my own machine. On LC 905 for sure, and probably on 950 also.

If Script Editor disassociation does happen, I advise immediate but

careful no-save quit or force quit, and pray that you're already in the
habit of backing up beforehand. Copy and paste the current script text to
an external text editor if necessary. Of course this particular bug just
might be able to defeat the safety of stack backups too in some situations,
but hey, that's why it's an extra-fabulous bug!

So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit

work-lossy. That could turn off both new and old users if they are the
humor-deficient type to frown on losing some work. But shucks, ain't no
thang! Only features features features (and new side projects) matter! Glad
we all agree on that.

Any reports or recipes on this issue? I'll post a report if there is

none. Thanks

I saw a similar error in earlier versions of LC9 where the script I was

editing was for a different object that what was indicate the Project
Browser. So the Project Browser was showing (highlighting) Object A but
actually thought it was on Object B.

It occurred fairly intermittently. I never developed a recipe and I

have not see this in the most recent releases (9.0.5 and 9.5.1)

Ditto. Hasn't happened for a while though.

Bob S



Of course, I am not saying that the bug isn't still in the current
releases, just that I have not noticed it in the current releases ;-)


___
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: Script Editor disassociates - a lossy LC IDE bug

2019-12-05 Thread Mark Wieder via use-livecode

On 12/5/19 5:11 PM, Tom Glod via use-livecode wrote:

Are you all on Mac?  This does not ring a bell.


Have seen that on linux although rarely and not recently. And of course 
didn't notice until after I had saved the script to disk and exited, so 
there's no recipe.


--
 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 disassociates - a lossy LC IDE bug

2019-12-05 Thread Tom Glod via use-livecode
Are you all on Mac?  This does not ring a bell.

On Thu, Dec 5, 2019 at 8:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 12/5/2019 6:38 PM, Bob Sneidar via use-livecode wrote:
> >
> >> On Dec 5, 2019, at 15:04 , Paul Dupuis via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> On 12/5/2019 5:42 PM, Curry Kenworthy via use-livecode wrote:
> >>> Wondering if this bug has already been reported?
> >>>
> >>> I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window
> seems to disassociate from the object being edited. Thus after this bug is
> triggered, any typed script changes may not really be applied and saved,
> although they are shown as applied. Next LC session, those changes are
> gone; the stack code is still as it was prior to the bug being triggered
> and prior to editing the script.
> >>>
> >>> An alternate form is that the script changes actually are applied, but
> in a bad way: first the script disassociates completely and is empty, then
> the empty script is saved, overwriting the previous script. Nice! (I think
> this is my favorite variation; if we're going to cause loss of work/code,
> might as well do it boldly and not beat around the bush.)
> >>>
> >>> I suspect this happens more on Mac than Windows, but since I don't
> have a recipe, not sure. I've seen this happen to other people rather than
> on my own machine. On LC 905 for sure, and probably on 950 also.
> >>>
> >>> If Script Editor disassociation does happen, I advise immediate but
> careful no-save quit or force quit, and pray that you're already in the
> habit of backing up beforehand. Copy and paste the current script text to
> an external text editor if necessary. Of course this particular bug just
> might be able to defeat the safety of stack backups too in some situations,
> but hey, that's why it's an extra-fabulous bug!
> >>>
> >>> So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit
> work-lossy. That could turn off both new and old users if they are the
> humor-deficient type to frown on losing some work. But shucks, ain't no
> thang! Only features features features (and new side projects) matter! Glad
> we all agree on that.
> >>>
> >>> Any reports or recipes on this issue? I'll post a report if there is
> none. Thanks
> >>>
> >> I saw a similar error in earlier versions of LC9 where the script I was
> editing was for a different object that what was indicate the Project
> Browser. So the Project Browser was showing (highlighting) Object A but
> actually thought it was on Object B.
> >>
> >> It occurred fairly intermittently. I never developed a recipe and I
> have not see this in the most recent releases (9.0.5 and 9.5.1)
> >>
> > Ditto. Hasn't happened for a while though.
> >
> > Bob S
> >
> >
>
> Of course, I am not saying that the bug isn't still in the current
> releases, just that I have not noticed it in the current releases ;-)
>
>
> ___
> 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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Office:226-706-9339
Mobile:226-706-9793
___
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 disassociates - a lossy LC IDE bug

2019-12-05 Thread Paul Dupuis via use-livecode

On 12/5/2019 6:38 PM, Bob Sneidar via use-livecode wrote:



On Dec 5, 2019, at 15:04 , Paul Dupuis via use-livecode 
 wrote:

On 12/5/2019 5:42 PM, Curry Kenworthy via use-livecode wrote:

Wondering if this bug has already been reported?

I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window seems to 
disassociate from the object being edited. Thus after this bug is triggered, 
any typed script changes may not really be applied and saved, although they are 
shown as applied. Next LC session, those changes are gone; the stack code is 
still as it was prior to the bug being triggered and prior to editing the 
script.

An alternate form is that the script changes actually are applied, but in a bad 
way: first the script disassociates completely and is empty, then the empty 
script is saved, overwriting the previous script. Nice! (I think this is my 
favorite variation; if we're going to cause loss of work/code, might as well do 
it boldly and not beat around the bush.)

I suspect this happens more on Mac than Windows, but since I don't have a 
recipe, not sure. I've seen this happen to other people rather than on my own 
machine. On LC 905 for sure, and probably on 950 also.

If Script Editor disassociation does happen, I advise immediate but careful 
no-save quit or force quit, and pray that you're already in the habit of 
backing up beforehand. Copy and paste the current script text to an external 
text editor if necessary. Of course this particular bug just might be able to 
defeat the safety of stack backups too in some situations, but hey, that's why 
it's an extra-fabulous bug!

So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit 
work-lossy. That could turn off both new and old users if they are the 
humor-deficient type to frown on losing some work. But shucks, ain't no thang! 
Only features features features (and new side projects) matter! Glad we all 
agree on that.

Any reports or recipes on this issue? I'll post a report if there is none. 
Thanks


I saw a similar error in earlier versions of LC9 where the script I was editing 
was for a different object that what was indicate the Project Browser. So the 
Project Browser was showing (highlighting) Object A but actually thought it was 
on Object B.

It occurred fairly intermittently. I never developed a recipe and I have not 
see this in the most recent releases (9.0.5 and 9.5.1)


Ditto. Hasn't happened for a while though.

Bob S




Of course, I am not saying that the bug isn't still in the current 
releases, just that I have not noticed it in the current releases ;-)



___
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 disassociates - a lossy LC IDE bug

2019-12-05 Thread Bob Sneidar via use-livecode



> On Dec 5, 2019, at 15:04 , Paul Dupuis via use-livecode 
>  wrote:
> 
> On 12/5/2019 5:42 PM, Curry Kenworthy via use-livecode wrote:
>> 
>> Wondering if this bug has already been reported?
>> 
>> I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window seems 
>> to disassociate from the object being edited. Thus after this bug is 
>> triggered, any typed script changes may not really be applied and saved, 
>> although they are shown as applied. Next LC session, those changes are gone; 
>> the stack code is still as it was prior to the bug being triggered and prior 
>> to editing the script.
>> 
>> An alternate form is that the script changes actually are applied, but in a 
>> bad way: first the script disassociates completely and is empty, then the 
>> empty script is saved, overwriting the previous script. Nice! (I think this 
>> is my favorite variation; if we're going to cause loss of work/code, might 
>> as well do it boldly and not beat around the bush.)
>> 
>> I suspect this happens more on Mac than Windows, but since I don't have a 
>> recipe, not sure. I've seen this happen to other people rather than on my 
>> own machine. On LC 905 for sure, and probably on 950 also.
>> 
>> If Script Editor disassociation does happen, I advise immediate but careful 
>> no-save quit or force quit, and pray that you're already in the habit of 
>> backing up beforehand. Copy and paste the current script text to an external 
>> text editor if necessary. Of course this particular bug just might be able 
>> to defeat the safety of stack backups too in some situations, but hey, 
>> that's why it's an extra-fabulous bug!
>> 
>> So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit 
>> work-lossy. That could turn off both new and old users if they are the 
>> humor-deficient type to frown on losing some work. But shucks, ain't no 
>> thang! Only features features features (and new side projects) matter! Glad 
>> we all agree on that.
>> 
>> Any reports or recipes on this issue? I'll post a report if there is none. 
>> Thanks
>> 
> 
> I saw a similar error in earlier versions of LC9 where the script I was 
> editing was for a different object that what was indicate the Project 
> Browser. So the Project Browser was showing (highlighting) Object A but 
> actually thought it was on Object B.
> 
> It occurred fairly intermittently. I never developed a recipe and I have not 
> see this in the most recent releases (9.0.5 and 9.5.1)
> 
Ditto. Hasn't happened for a while though. 

Bob S



___
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 disassociates - a lossy LC IDE bug

2019-12-05 Thread Paul Dupuis via use-livecode

On 12/5/2019 5:42 PM, Curry Kenworthy via use-livecode wrote:


Wondering if this bug has already been reported?

I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window 
seems to disassociate from the object being edited. Thus after this 
bug is triggered, any typed script changes may not really be applied 
and saved, although they are shown as applied. Next LC session, those 
changes are gone; the stack code is still as it was prior to the bug 
being triggered and prior to editing the script.


An alternate form is that the script changes actually are applied, but 
in a bad way: first the script disassociates completely and is empty, 
then the empty script is saved, overwriting the previous script. Nice! 
(I think this is my favorite variation; if we're going to cause loss 
of work/code, might as well do it boldly and not beat around the bush.)


I suspect this happens more on Mac than Windows, but since I don't 
have a recipe, not sure. I've seen this happen to other people rather 
than on my own machine. On LC 905 for sure, and probably on 950 also.


If Script Editor disassociation does happen, I advise immediate but 
careful no-save quit or force quit, and pray that you're already in 
the habit of backing up beforehand. Copy and paste the current script 
text to an external text editor if necessary. Of course this 
particular bug just might be able to defeat the safety of stack 
backups too in some situations, but hey, that's why it's an 
extra-fabulous bug!


So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit 
work-lossy. That could turn off both new and old users if they are the 
humor-deficient type to frown on losing some work. But shucks, ain't 
no thang! Only features features features (and new side projects) 
matter! Glad we all agree on that.


Any reports or recipes on this issue? I'll post a report if there is 
none. Thanks




I saw a similar error in earlier versions of LC9 where the script I was 
editing was for a different object that what was indicate the Project 
Browser. So the Project Browser was showing (highlighting) Object A but 
actually thought it was on Object B.


It occurred fairly intermittently. I never developed a recipe and I have 
not see this in the most recent releases (9.0.5 and 9.5.1)


___
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


Script Editor disassociates - a lossy LC IDE bug

2019-12-05 Thread Curry Kenworthy via use-livecode



Wondering if this bug has already been reported?

I've seen a wonderful LC 9 IDE bug: sometimes the Script Editor window 
seems to disassociate from the object being edited. Thus after this bug 
is triggered, any typed script changes may not really be applied and 
saved, although they are shown as applied. Next LC session, those 
changes are gone; the stack code is still as it was prior to the bug 
being triggered and prior to editing the script.


An alternate form is that the script changes actually are applied, but 
in a bad way: first the script disassociates completely and is empty, 
then the empty script is saved, overwriting the previous script. Nice! 
(I think this is my favorite variation; if we're going to cause loss of 
work/code, might as well do it boldly and not beat around the bush.)


I suspect this happens more on Mac than Windows, but since I don't have 
a recipe, not sure. I've seen this happen to other people rather than on 
my own machine. On LC 905 for sure, and probably on 950 also.


If Script Editor disassociation does happen, I advise immediate but 
careful no-save quit or force quit, and pray that you're already in the 
habit of backing up beforehand. Copy and paste the current script text 
to an external text editor if necessary. Of course this particular bug 
just might be able to defeat the safety of stack backups too in some 
situations, but hey, that's why it's an extra-fabulous bug!


So, in addition to being a bit crashy and glitchy, the 9 IDE is a bit 
work-lossy. That could turn off both new and old users if they are the 
humor-deficient type to frown on losing some work. But shucks, ain't no 
thang! Only features features features (and new side projects) matter! 
Glad we all agree on that.


Any reports or recipes on this issue? I'll post a report if there is 
none. Thanks


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: iOS dark mode

2019-12-05 Thread Andrew Bell via use-livecode

Thank you Trevor! Adding this to my info.plist opted out of Dark Mode:
UIUserInterfaceStyle
Light

Apple's ominous note at the end of that article gives me the  
impression that before too long (iOS 14?) this override will get the  
app rejected:
"Supporting Dark Mode is strongly encouraged. Use the  
UIUserInterfaceStyle key to opt out only temporarily while you work on  
improvements to your app's Dark Mode support."


--Andrew Bell




Date: Wed, 4 Dec 2019 14:46:10 -0600
From: Trevor DeVore 
To: How to use LiveCode 
Subject: Re: iOS dark mode

On Wed, Dec 4, 2019 at 2:30 PM Andrew Bell via use-livecode <
use-livecode@lists.runrev.com> wrote:


Is there a way to determine if an iOS device has dark mode ("Dark
Appearance") enabled from within a LiveCode app?

The inherited default text color of a field is black, but is changed
to white by the OS when this mode is enabled (on a white background in
this case which makes it appear invisible). This seems to only affect
native mobile text fields, but not LC text fields.

There is a feature enhancement to support dark mode for macOS, but I
didn't see any reports for iOS.
https://quality.livecode.com/show_bug.cgi?id=1

I'm not asking for an engine change, just curious if there is a way to
check this so I can code around it. Perhaps mergNotify?



I don't know of a way to check this from within LiveCode using existing
tools. There is an API for checking which is documented here:

https://developer.apple.com/documentation/uikit/uitraitcollection/1651063-userinterfacestyle?language=objc

It should be possible to wrap that API using LiveCode Builder. From what
I've read, I think you also need to respond to a trailCollectionDidChange
message in case the user changes the setting while your app is open:

https://developer.apple.com/documentation/uikit/uitraitenvironment/1623516-traitcollectiondidchange?language=objc

The easier (temporary) solution would be to tell the OS to use light
appearance for your app. It looks like there is an Info.plist key that you
can add which will force your app to use the light appearance. Perhaps that
will help in your situation?

https://developer.apple.com/documentation/xcode/supporting_dark_mode_in_your_interface/choosing_a_specific_interface_style_for_your_ios_app?language=objc#3234550

--
Trevor DeVore
ScreenSteps
www.screensteps.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: XCode 11 requirements

2019-12-05 Thread Matthias Rebbe via use-livecode
If your Mac runs Mojave and is up to date then you should have 10.14.6 already 
installed.
If you still have a lower Mojave version installed then you could find the 
updates for the 10.14.x among the updates for older and news os here

https://support.apple.com/downloads/macos 


Btw the update from 10.14.2 to 10.14.3 can be found here 
https://support.apple.com/kb/DL1991?viewlocale=en_US&locale=en_US 




Matthias Rebbe

free tools for Livecoders:
InstaMaker 
WinSignMaker Mac 

> Am 05.12.2019 um 20:35 schrieb J. Landman Gay via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> In LC 9.6 (dp 1) I get a warning that I can't use XCode 11 (which isn't 
> installed yet anyway) unless I update to Mac OS 10.14.3. My Mac is up to date 
> as far as I know and there is no OS 10.14.3 available in the Mac App Store. I 
> can't update to Catalina until some of my critical software becomes 
> compatible.
> 
> Is there a way to use XCode 10.1 in Mojave with LC 9.6?
> -- 
> 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: XCode 11 requirements

2019-12-05 Thread Richmond via use-livecode

That's odd as my Mac Mini is running on MacOS 10.14.6; and as far
as I remember it passed through 10.14.3 to get there.

Richmond.

On 5.12.19 21:35, J. Landman Gay via use-livecode wrote:
In LC 9.6 (dp 1) I get a warning that I can't use XCode 11 (which 
isn't installed yet anyway) unless I update to Mac OS 10.14.3. My Mac 
is up to date as far as I know and there is no OS 10.14.3 available in 
the Mac App Store. I can't update to Catalina until some of my 
critical software becomes compatible.


Is there a way to use XCode 10.1 in Mojave with LC 9.6?



___
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


XCode 11 requirements

2019-12-05 Thread J. Landman Gay via use-livecode
In LC 9.6 (dp 1) I get a warning that I can't use XCode 11 (which isn't 
installed yet anyway) unless I update to Mac OS 10.14.3. My Mac is up to 
date as far as I know and there is no OS 10.14.3 available in the Mac 
App Store. I can't update to Catalina until some of my critical software 
becomes compatible.


Is there a way to use XCode 10.1 in Mojave with LC 9.6?
--
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


scrollbars on iOS

2019-12-05 Thread Ben Rubinstein via use-livecode
I'm trying to make a very simple app featuring a large browser widget in a 
small group. Not entirely to my surprise, the browser widget is displayed over 
the scrollbars of the group (it's cropped to the outer borders of the group, 
but not taking account of the scrollbars).


That's OK I thought (this app is for my own use) - I'll tell the group not to 
bother displaying scrollbars, and add my own scrollbars outside it, to scroll 
the group. This works fine on desktop. On iOS (which is what I want it for) 
the scrollbars sort of work - but they have tiny 'thumbs', the draggable 
moving bit.


I was surprised because I know I've done another iOS app on which the 
scrollbars seemed to behave normally (with proportional thumbs). When I went 
to look however, I found that this was a case where I'd had a group displaying 
its own scrollbars, and that seemed fine.


Is there some trick to make normal scrollbars work OK on mobile (specifically 
iOS)?


TIA,

Ben

___
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: Achilles Heel of Livecode

2019-12-05 Thread Tom Glod via use-livecode
hehehe. its one of those paradoxical things .. its so badthat
its so good.

On Thu, Dec 5, 2019 at 9:39 AM Rick Harrison via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Tom,
>
> Your comment enticed me to take a look at that PDF.
> Someone put a lot of work into it for sure!
>
> Apparently they wanted a magazine format for it.
> Perhaps that’s what they are used to doing for their
> old day job?
>
> My eyes still hurt from trying to look at all of the
> information there.  Information overload for me.
>
> Rick
>
> > On Dec 5, 2019, at 7:54 AM, Tom Glod via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Wow...I have never ever seen a website like that.  The PDF is the
> most
> > incredible piece of typesetting the world has ever seen.
>
> ___
> 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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Office:226-706-9339
Mobile:226-706-9793
___
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: Connecting LC to Xcode

2019-12-05 Thread panagiotis merakos via use-livecode
Indeed, completely re-installing Xcode10.1 at this point will probably fix
the problem.

Another user in the forum had *exactly* the same problem after following
the instructions, and re-installing Xcode10.1 fixed the issue.

Kind regards,
Panos
--

On Thu, 5 Dec 2019 at 07:33, Jjs via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Maybe a deinstall of all xcode versions, reboot, reinstall may do a
> miracle. Seems like strange failures.
>
> Marty Knapp via use-livecode  schreef op 5
> december 2019 00:48:01 CET:
> >OK I took those steps but now when I launch Simulator I get this error:
> >
> >“Unable to boot device because it cannot be located on disk. Us eat
> >device manager in Xcode of the simctl command line tool to either
> >delete the device properly or erase the contents and settings.”
> >
> >I try selecting a device from the Hardware menu and can sometimes get
> >one to load but then when I test from LC I get this error:
> >
> >“Unable to start simulator: 634,0,0,unknown C++ exception
> >573,228,1,revIPhoneSetSimulatorSDK"
> >
> >There is a new Developer folder (I renamed the folder for 11.2). I
> >looked in Preferences and removed everything that looked like it
> >belonged to Xcode.
> >
> >> On Dec 4, 2019, at 11:36 AM, panagiotis merakos via use-livecode
> > wrote:
> >>
> >> Hello Marty,
> >>
> >> Hehe, OK, I think I know where the problem is. I had the same problem
> >and
> >> spent a lot of time trying to figure out the problem, as the error
> >message
> >> from the simulator is not informative at all. So, short description
> >of the
> >> problem:
> >>
> >> By installing xcode11.x and its additional components, a couple of
> >new
> >> subfolders were created in /Library/Developer/* folder. These new
> >files
> >> contain the new CoreSimulator framework (of xcode11.x), which
> >includes some
> >> changes. One of these is that it no longer allows installing apps to
> >the
> >> simulator that do not include a particular key in the plist. Even if
> >you
> >> uninstall Xcode 11 and install Xcode 10.1, this file is not replaced
> >by
> >> Xcode10.1's equivalent (because the one from Xcode11 is newer, so it
> >does
> >> not allow older ones to overwrite it).
> >>
> >> Solution:
> >>
> >> 1. Open Finder, and choose (from Finder's menubar) Go -> Go to Folder
> >and
> >> enter /Library/Developer/
> >> 2. Delete the /Library/Developer/ folder (or rename it to
> >> /Library/XCode11_Developer/)
> >> 3. In the terminal, type sudo xcode-select --install and press enter.
> >This
> >> will show a dialog asking the user to agree to xcode's terms and
> >conditions
> >> and then to install the additional components. Click "I agree" and
> >then
> >> "Yes install them"
> >> 4. This will create a new folder /Library/Developer/, which will
> >contain
> >> the correct additional components (i.e. including the CoreSimulator
> >> framework) from Xcode 10.1
> >> 5. Now type in the the Terminal sudo xcode-select -s
> >
> >>
> >> This will hopefully work. Then, make sure you follow the instructions
> >from
> >> the previous post (i.e. to launch the simulator first and then click
> >"Test"
> >> in LC)
> >>
> >> Kind regards,
> >> Panos
> >> --
> >>
> >> On Wed, 4 Dec 2019 at 19:55, Marty Knapp via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >>> Yes those are the steps I’ve tried, only using Xcode 10.1 (couldn’t
> >get LC
> >>> to accept 11.2). When I click the “Test” button it starts going
> >through the
> >>> process of prepping the app then errors out with the message “Unable
> >to
> >>> start simulation: Failed to install the requested application”
> >>>
> >>> If I change the test target to my actual iPhone it installs it fine,
> >so I
> >>> guess I’ll just do that.
> >>>
>  On Dec 3, 2019, at 11:25 PM, panagiotis merakos via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> 
>  Hello all,
> 
>  I usually follow these steps, and I almost never have problems with
> >the
>  simulator:
> 
>  (Note: these instructions are for Xcode11.1, but are applicable to
> >any
>  Xcode version)
> 
>  0. Make sure the command line tools that will be used by LiveCode
> >are the
>  ones of the correct Xcode:
>  (Launch Xcode 11.1, go to Xcode's menubar and choose Xcode->
> >>> Preferences->
>  Locations and in the Command Line Tools dropdown choose "Xcode
> >11.1")
> 
>  1. Open the Simulator from Xcode11.1 (Launch Xcode, go to Xcode's
> >menubar
>  and choose
>  Xcode -> Open Developer Tool -> Simulator
> 
>  2. Wait until the simulator fully loads, until it shows the
> >device's Home
>  screen
> 
>  3. You can change device by clicking on the Simulator's app
> >menubar:
> 
>  Hardware -> Device -> iOS 13.1 -> 
> 
>  4. Again, wait until the new simulator device fully loads, until it
> >shows
>  the
>  device's Home screen
> 
>  5. Now go back to LiveCode, choose the iOS simul

Re: Achilles Heel of Livecode

2019-12-05 Thread Rick Harrison via use-livecode
Hi Tom,

Your comment enticed me to take a look at that PDF.
Someone put a lot of work into it for sure!

Apparently they wanted a magazine format for it.
Perhaps that’s what they are used to doing for their
old day job?

My eyes still hurt from trying to look at all of the
information there.  Information overload for me. 

Rick

> On Dec 5, 2019, at 7:54 AM, Tom Glod via use-livecode 
>  wrote:
> 
> Wow...I have never ever seen a website like that.  The PDF is the most
> incredible piece of typesetting the world has ever seen.

___
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: Achilles Heel of Livecode

2019-12-05 Thread Erik Beugelaar via use-livecode
LOL  ;-)


On 05/12/2019, 13:56, "use-livecode on behalf of Tom Glod via use-livecode" 
 wrote:

Wow...I have never ever seen a website like that.  The PDF is the most
incredible piece of typesetting the world has ever seen.

On Tue, Dec 3, 2019 at 7:11 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 12/3/19 3:40 PM, Erik Beugelaar via use-livecode wrote:
> > My comment was meant as a joke by the way not to promote the product!The
> brochure was funny to me because of the used graphics.
>
> Yes, I got the part about it being a joke. And that pdf is unbearably
> hard to read. Nonetheless, there are some *very* interesting ideas there.
>
> --
>   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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Office:226-706-9339
Mobile:226-706-9793
___
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: Achilles Heel of Livecode

2019-12-05 Thread Tom Glod via use-livecode
Wow...I have never ever seen a website like that.  The PDF is the most
incredible piece of typesetting the world has ever seen.

On Tue, Dec 3, 2019 at 7:11 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 12/3/19 3:40 PM, Erik Beugelaar via use-livecode wrote:
> > My comment was meant as a joke by the way not to promote the product!The
> brochure was funny to me because of the used graphics.
>
> Yes, I got the part about it being a joke. And that pdf is unbearably
> hard to read. Nonetheless, there are some *very* interesting ideas there.
>
> --
>   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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Office:226-706-9339
Mobile:226-706-9793
___
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


Map widget and user location

2019-12-05 Thread Tore Nilsen via use-livecode

I am trying to familiarise myself with the map widget. What I want to do is to 
get the coordinates for the user location and to set a pin for this location. 
As it is possible to show the user location in the map widget, my original idea 
was to retrieve the information from the widget and apply it to a marker in a 
mouseUp handler. 

If anyone could point me in the right direction I would be a very happy man.

Best regards
Tore Nilsen
___
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