Re: Standalones and the defaultFolder

[Mark Waddingham via use-livecode]

On 2019-12-15 13:29, Paul Dupuis via use-livecode wrote:

Just a reminder that the files(,"detailed") (i.e. the detailed
files) and the detailed folders are NOT Unicode aware. If you have any
Unicode characters in path or the file names, they will be returned as
URLEncoded question marks making matching a specific name in the
returned data difficult.

https://quality.livecode.com/show_bug.cgi?id=22213


This will be resolved from 9.6-dp-2: 



Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Something wrong with LiveCode 9.5.1

[Paul Dupuis via use-livecode]

Okay, I blame a LONG day and bad memory.

 I went and found our testing notes:

macOS name    signed notarized stapled
10.9  Mavricks    OK FAIL  FAIL
10.10 Yosemite    OK FAIL  FAIL
10.11 El Capitan  OK     FAIL  FAIL
10.12 Sierra  OK OK    OK
10.13 High Sierra OK OK    OK
10.14 Mojave  OK OK    OK
10.15 Catalina    *  OK    OK


The divider is Sierra and above: Notarized DMGs are good. El Capatan and 
below, Notarized DMGs are bad.


My bad memory. Sorry to cause unnecessary concern.


On 12/16/2019 4:29 PM, Paul Dupuis via use-livecode wrote:

On 12/16/2019 3:58 PM, Jerry Jensen wrote:
This is the first time I have heard that anything notarized will not 
open in Sierra. I have been watching the whole notarization topic, 
but apparently not closely enough. Could you point me to some info 
from Apple about what is -not- supported in Sierra?


I support an entire flock of Sierra computers. We are preparing to 
roll out Mojave soon. I guess that better be done ASAP.




I can't point you to any Apple materials as we discovered this once we 
notarized out DMG for Catalina and was performing final installation 
testing on Catalina and other versions of macOS


You can download the macOS DMG for our app at 
http://www.researchware.com/downloads.html


Scroll down the page to the download links. You will see ONE DMG for 
Catalina and another DNG for other version of OSX. Download the 
Catalina DMG and you will find the notarized DMG opens on Catalina, 
Mojave, and High Sierra, but throws and error on Sierra and below.


We choose to Notarize the DMG rather than the installer app. I realize 
while Apple allows this (currently) is is not what their documentation 
on Notarization speaks to which is Notarizing the APP and performing 
drag-installs from the DMG rather than using an Installer app.


Our application HyperRESEARCH, our Installer are both code signed. The 
Catalina DMG is code signed, notarized, and stapled. The non-Catalina 
DMG is not code signed (and not notarized).


We used this excellent guidance to figure out how to do notarization: 
http://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore


___
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: Something wrong with LiveCode 9.5.1

[Jerry Jensen via use-livecode]

Thanks Paul. I’ll be testing. I don’t have anything but a Sierra install handy. 
Yet.
.Jerry

> On Dec 16, 2019, at 1:29 PM, Paul Dupuis  wrote:
> 
> On 12/16/2019 3:58 PM, Jerry Jensen wrote:
>> This is the first time I have heard that anything notarized will not open in 
>> Sierra. I have been watching the whole notarization topic, but apparently 
>> not closely enough. Could you point me to some info from Apple about what is 
>> -not- supported in Sierra?
>> 
>> I support an entire flock of Sierra computers. We are preparing to roll out 
>> Mojave soon. I guess that better be done ASAP.
>> 
> 
> I can't point you to any Apple materials as we discovered this once we 
> notarized out DMG for Catalina and was performing final installation testing 
> on Catalina and other versions of macOS
> 
> You can download the macOS DMG for our app at 
> http://www.researchware.com/downloads.html
> 
> Scroll down the page to the download links. You will see ONE DMG for Catalina 
> and another DNG for other version of OSX. Download the Catalina DMG and you 
> will find the notarized DMG opens on Catalina, Mojave, and High Sierra, but 
> throws and error on Sierra and below.
> 
> We choose to Notarize the DMG rather than the installer app. I realize while 
> Apple allows this (currently) is is not what their documentation on 
> Notarization speaks to which is Notarizing the APP and performing 
> drag-installs from the DMG rather than using an Installer app.
> 
> Our application HyperRESEARCH, our Installer are both code signed. The 
> Catalina DMG is code signed, notarized, and stapled. The non-Catalina DMG is 
> not code signed (and not notarized).
> 
> We used this excellent guidance to figure out how to do notarization: 
> http://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore
> 


___
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: Something wrong with LiveCode 9.5.1

[Paul Dupuis via use-livecode]

On 12/16/2019 3:58 PM, Jerry Jensen wrote:

This is the first time I have heard that anything notarized will not open in 
Sierra. I have been watching the whole notarization topic, but apparently not 
closely enough. Could you point me to some info from Apple about what is -not- 
supported in Sierra?

I support an entire flock of Sierra computers. We are preparing to roll out 
Mojave soon. I guess that better be done ASAP.



I can't point you to any Apple materials as we discovered this once we 
notarized out DMG for Catalina and was performing final installation 
testing on Catalina and other versions of macOS


You can download the macOS DMG for our app at 
http://www.researchware.com/downloads.html


Scroll down the page to the download links. You will see ONE DMG for 
Catalina and another DNG for other version of OSX. Download the Catalina 
DMG and you will find the notarized DMG opens on Catalina, Mojave, and 
High Sierra, but throws and error on Sierra and below.


We choose to Notarize the DMG rather than the installer app. I realize 
while Apple allows this (currently) is is not what their documentation 
on Notarization speaks to which is Notarizing the APP and performing 
drag-installs from the DMG rather than using an Installer app.


Our application HyperRESEARCH, our Installer are both code signed. The 
Catalina DMG is code signed, notarized, and stapled. The non-Catalina 
DMG is not code signed (and not notarized).


We used this excellent guidance to figure out how to do notarization: 
http://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore


___
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: Something wrong with LiveCode 9.5.1

[Jerry Jensen via use-livecode]

This is the first time I have heard that anything notarized will not open in 
Sierra. I have been watching the whole notarization topic, but apparently not 
closely enough. Could you point me to some info from Apple about what is -not- 
supported in Sierra? 

I support an entire flock of Sierra computers. We are preparing to roll out 
Mojave soon. I guess that better be done ASAP.

Thanks,
.Jerry

> On Dec 16, 2019, at 12:24 PM, Paul Dupuis via use-livecode 
>  wrote:

> I think that was the point. LC, Ltd forgot to Notarize the 9.5.1 STABLE 
> version. However, this turns into more of a problem that you might think. A 
> notarized DMG will open under High Sierra to Catalina, but fails on any 
> version below High Sierra, so you need to provide both Notarized and 
> non-Notarized versions to if you support versions of the macOS before High 
> Sierra. Technical 9.5.1 still supports Mavericks so the 
> downloads.livecode.com page needs to change to list 2 versions - a non 
> notarized version for Mavericks to Sierra and a Notarized version for High 
> Sierra to Calalina.

___
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: Something wrong with LiveCode 9.5.1

[Brian Milby via use-livecode]

My guess is that 9.6 will be the first to officially support Catalina and get 
the notarization treatment.  I think it was hinted at in the release email for 
the first DP.

Thanks,
Brian
On Dec 16, 2019, 3:20 PM -0500, Richmond via use-livecode 
, wrote:
> Thank you for that; it was a great help.
>
> HOWEVER, that is the version of LiveCode 9.5.1 just released and
> labelled 'stable.'
>
> On 16.12.19 22:11, Tore Nilsen via use-livecode wrote:
> > This is not very odd. It is the way MacOs now handles all applications that 
> > are not notarized. I would suspect this kind of message for any dp or rc 
> > version of LiveCode, but not for a stable version. You can get around this 
> > either by right-clicking the application and choose «Open» from the local 
> > menu. You will then have an option to choose to open this application. Once 
> > you have done, the message will not reappear when you start LiveCode.
> >
> > Tore Nilsen
> >
> > > 16. des. 2019 kl. 21:03 skrev Richmond via use-livecode 
> > > :
> > >
> > > I am afraid that I have to report something very odd indeed
> > > about LiveCode 9.5.1 stable, as on launching I get a windows that states:
> > >
> > > [ Mac OS 10.15.2 ]
> > >
> > > " "LiveCode Community 9.5.1" can't be
> > > opened because Apple cannot check it for
> > > malicious software.
> > >
> > > "This software needs to be updated. Contact the
> > > developer for more information."
> > >
> > > "Pretty" picture here:
> > >
> > > http://forums.livecode.com/viewtopic.php?f=4&t=33440#p186161
> > >
> > > Best, Richmond.
> > >
> > > ___
> > > use-livecode mailing list
> > > use-livecode@lists.runrev.com
> > > Please visit this url to subscribe, unsubscribe and manage your 
> > > subscription preferences:
> > > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your 
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Something wrong with LiveCode 9.5.1

[Paul Dupuis via use-livecode]

On 12/16/2019 3:11 PM, Tore Nilsen via use-livecode wrote:

I would suspect this kind of message for any dp or rc version of LiveCode, but 
not for a stable version.


I think that was the point. LC, Ltd forgot to Notarize the 9.5.1 STABLE 
version. However, this turns into more of a problem that you might 
think. A notarized DMG will open under High Sierra to Catalina, but 
fails on any version below High Sierra, so you need to provide both 
Notarized and non-Notarized versions to if you support versions of the 
macOS before High Sierra. Technical 9.5.1 still supports Mavericks so 
the downloads.livecode.com page needs to change to list 2 versions - a 
non notarized version for Mavericks to Sierra and a Notarized version 
for High Sierra to Calalina.


Which is probably why they did not bother to Notarize it.

___
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: Something wrong with LiveCode 9.5.1

[Richmond via use-livecode]

Thank you for that; it was a great help.

HOWEVER, that is the version of LiveCode 9.5.1 just released and 
labelled 'stable.'


On 16.12.19 22:11, Tore Nilsen via use-livecode wrote:

This is not very odd. It is the way MacOs now handles all applications that are 
not notarized. I would suspect this kind of message for any dp or rc version of 
LiveCode, but not for a stable version. You can get around this either by 
right-clicking the application and choose «Open»  from the local menu. You will 
then have an option to choose to open this application. Once you have done, the 
message will not reappear when you start LiveCode.

Tore Nilsen


16. des. 2019 kl. 21:03 skrev Richmond via use-livecode 
:

I am afraid that I have to report something very odd indeed
about LiveCode 9.5.1 stable, as on launching I get a windows that states:

[ Mac OS 10.15.2 ]

" "LiveCode Community 9.5.1" can't be
opened because Apple cannot check it for
malicious software.

"This software needs to be updated. Contact the
developer for more information."

"Pretty" picture here:

http://forums.livecode.com/viewtopic.php?f=4&t=33440#p186161

Best, Richmond.

___
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: Something wrong with LiveCode 9.5.1

[Tore Nilsen via use-livecode]

This is not very odd. It is the way MacOs now handles all applications that are 
not notarized. I would suspect this kind of message for any dp or rc version of 
LiveCode, but not for a stable version. You can get around this either by 
right-clicking the application and choose «Open»  from the local menu. You will 
then have an option to choose to open this application. Once you have done, the 
message will not reappear when you start LiveCode.

Tore Nilsen

> 16. des. 2019 kl. 21:03 skrev Richmond via use-livecode 
> :
> 
> I am afraid that I have to report something very odd indeed
> about LiveCode 9.5.1 stable, as on launching I get a windows that states:
> 
> [ Mac OS 10.15.2 ]
> 
> " "LiveCode Community 9.5.1" can't be
> opened because Apple cannot check it for
> malicious software.
> 
> "This software needs to be updated. Contact the
> developer for more information."
> 
> "Pretty" picture here:
> 
> http://forums.livecode.com/viewtopic.php?f=4&t=33440#p186161
> 
> Best, Richmond.
> 
> ___
> 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: Something wrong with LiveCode 9.5.1

[Matthias Rebbe via use-livecode]

If i remember right you can go to System Preferences -> Security -> Firewall. 
There you should be able to allow the system to open the last blocked app.

Matthias Rebbe

free tools for Livecoders:
InstaMaker 
WinSignMaker Mac 

> Am 16.12.2019 um 21:03 schrieb Richmond via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> I am afraid that I have to report something very odd indeed
> about LiveCode 9.5.1 stable, as on launching I get a windows that states:
> 
> [ Mac OS 10.15.2 ]
> 
> " "LiveCode Community 9.5.1" can't be
> opened because Apple cannot check it for
> malicious software.
> 
> "This software needs to be updated. Contact the
> developer for more information."
> 
> "Pretty" picture here:
> 
> http://forums.livecode.com/viewtopic.php?f=4&t=33440#p186161 
> 
> 
> Best, Richmond.
> 
> ___
> 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

Something wrong with LiveCode 9.5.1

[Richmond via use-livecode]

I am afraid that I have to report something very odd indeed
about LiveCode 9.5.1 stable, as on launching I get a windows that states:

[ Mac OS 10.15.2 ]

" "LiveCode Community 9.5.1" can't be
opened because Apple cannot check it for
malicious software.

"This software needs to be updated. Contact the
developer for more information."

"Pretty" picture here:

http://forums.livecode.com/viewtopic.php?f=4&t=33440#p186161

Best, Richmond.

___
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: Standalones and the defaultFolder

[Bob Sneidar via use-livecode]

I came to this conclusion over a year ago and have had refactoring away from it 
on the back burner. No longer. I went through my code and divorced myself from 
this addictive coding habit. 

Bob S


> On Dec 16, 2019, at 09:15 , Mark Waddingham via use-livecode 
>  wrote:
> 
> Upshot - never use the defaultFolder to find stackfiles - unless they are 
> passed in by the user as arguments in a command-line context. There's 
> 'specialFolderPath's for various places these days (most noticeable resources 
> and engine); but you can also just grok the filename property of your 
> mainstack too. (The stackFiles property can be useful here too - this allows 
> mapping arbitrary stack names to filepaths, which if relative are relative to 
> the stack on which the stackFiles property is set).
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.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

[ANN] This Week in LiveCode 206

[panagiotis merakos via use-livecode]

Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #206 here: http://bit.ly/2PSPZEK

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to you e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.


-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
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: Standalones and the defaultFolder

[Mark Waddingham via use-livecode]

On 2019-12-16 16:54, J. Landman Gay via use-livecode wrote:

On launch, the defaultfolder is set to the folder containing the
executable. On desktop this is the folder containing livecode. In a
standalone it's the folder containing the app (which on Mac is inside
the bundle.) But any time you change the defaultfolder it stays there,
it doesn't set itself back automatically.


The latter part is true, the former isn't necessarily so :)

I think the 'problem' here is that there is an expectation that the 
defaultFolder is something you can rely on to be known when your app is 
run but it isn't (nor has it ever been) - the engine doesn't touch the 
defaultFolder on startup, it is what the OS/environment decides it is.


For example if you launch a LiveCode app from Terminal (or platform 
equivalent) the default folder will be that which was in place in 
Terminal when you launched it (i.e. what your user - not you - decided 
it to be).


Launching from Finder (or Explorer or wherever) might make it appear 
like it should be a standard place - but that will depend on what OS you 
are running and even which version (I'm almost sure Finder changed from 
being the MacOS folder inside an app bundle to the folder containing the 
bundle at some point - or vice-versa - but don't quote me on that).


If the engine did fettle with the defaultFolder at all, then writing any 
sort of shell command (or app launchable from the command-line) which 
allowed relative paths in arguments would be impossible.


Upshot - never use the defaultFolder to find stackfiles - unless they 
are passed in by the user as arguments in a command-line context. 
There's 'specialFolderPath's for various places these days (most 
noticeable resources and engine); but you can also just grok the 
filename property of your mainstack too. (The stackFiles property can be 
useful here too - this allows mapping arbitrary stack names to 
filepaths, which if relative are relative to the stack on which the 
stackFiles property is set).


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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: Standalones and the defaultFolder

[J. Landman Gay via use-livecode]

On launch, the defaultfolder is set to the folder containing the 
executable. On desktop this is the folder containing livecode. In a 
standalone it's the folder containing the app (which on Mac is inside the 
bundle.) But any time you change the defaultfolder it stays there, it 
doesn't set itself back automatically.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 16, 2019 9:57:08 AM Bob Sneidar via use-livecode 
 wrote:


Thanks JB. Getting and setting the default folder was not the issue. The 
issue is that in a wondows standalone, a stack in the same folder as the 
executable could not be opened by script eg. open stack "Devices". This 
seems to be a new development, as I am fairly certain this worked fine in 
the past. ALL stack files in a standalone ought to be discoverable no 
matter what the defaultFolder is.


Bob S


On Dec 14, 2019, at 04:27 , JB via use-livecode 
 wrote:


I am not using Windows or the version of Livecode you are
using so I am not testing this but when it comes to using
paths you might want to make sure what path is being
provided.

If the path returned includes a file name then it might
not work properly for listing that directory because it
is trying to list the directory of the file name instead
of the folder the file is in.

This behavior could also cause your program to not
see something making you think the default folder
is not working properly when it might be the path
the default folder is using ends with the file name.

JB



___
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: Standalones and the defaultFolder

[JB via use-livecode]

Thanks for the info!  I hope you solve the problem.

JB


> On Dec 16, 2019, at 7:55 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> Thanks JB. Getting and setting the default folder was not the issue. The 
> issue is that in a wondows standalone, a stack in the same folder as the 
> executable could not be opened by script eg. open stack "Devices". This seems 
> to be a new development, as I am fairly certain this worked fine in the past. 
> ALL stack files in a standalone ought to be discoverable no matter what the 
> defaultFolder is. 
> 
> Bob S
> 
> 
>> On Dec 14, 2019, at 04:27 , JB via use-livecode 
>>  wrote:
>> 
>> I am not using Windows or the version of Livecode you are
>> using so I am not testing this but when it comes to using
>> paths you might want to make sure what path is being
>> provided.
>> 
>> If the path returned includes a file name then it might
>> not work properly for listing that directory because it
>> is trying to list the directory of the file name instead
>> of the folder the file is in.
>> 
>> This behavior could also cause your program to not
>> see something making you think the default folder
>> is not working properly when it might be the path
>> the default folder is using ends with the file name.
>> 
>> JB
> 
> 
> ___
> 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: Standalones and the defaultFolder

[Bob Sneidar via use-livecode]

Thanks JB. Getting and setting the default folder was not the issue. The issue 
is that in a wondows standalone, a stack in the same folder as the executable 
could not be opened by script eg. open stack "Devices". This seems to be a new 
development, as I am fairly certain this worked fine in the past. ALL stack 
files in a standalone ought to be discoverable no matter what the defaultFolder 
is. 

Bob S


> On Dec 14, 2019, at 04:27 , JB via use-livecode 
>  wrote:
> 
> I am not using Windows or the version of Livecode you are
> using so I am not testing this but when it comes to using
> paths you might want to make sure what path is being
> provided.
> 
> If the path returned includes a file name then it might
> not work properly for listing that directory because it
> is trying to list the directory of the file name instead
> of the folder the file is in.
> 
> This behavior could also cause your program to not
> see something making you think the default folder
> is not working properly when it might be the path
> the default folder is using ends with the file name.
> 
> JB


___
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: get URL problems

[Richard Gaskin via use-livecode]

What does "the result" show when queried immediately after "get url..."?

--
 Richard Gaskin
 Fourth World Systems


FlexibleLearning.com wrote:

Why can I 'launch' this url but not 'get' it?

put
"https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=MSFT&ap
ikey=demo" into tURL
launch url tURL --| Works fine, page loads entirely as expected in default
web browser
get url tURL --| Returns empty, nada, not a sausage
put it into tJSON 



I am using libUrl v1.1.6 300506


___
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: Standalones and the defaultFolder

[Bob Sneidar via use-livecode]

Oh sweet thanks. 

Bob S


> On Dec 14, 2019, at 17:33 , Alex Tweedly via use-livecode 
>  wrote:
> 
>>> 
>>> On Dec 13, 2019, at 3:21 PM, Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
>>> Thanks for the confirmation Tom. I did see two places in my code that I 
>>> have to set the default folder, so I just reset it when I am done. Same 
>>> thing, getting list of files. There may have been some discussion in the 
>>> past about a files command where the path could be passed, but that's not 
>>> close to any priority.
> 
> Hi Bob. Since 8.1 the files command allows the directory to be provided, e.g.
> 
>put files("..") into temp
> 
>put files("/user/alex", "detailed") into temp
> 
> etc. Also works for  folders()
> 
> Alex.


___
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

[ANN] Release 9.5.1

[panagiotis merakos via use-livecode]

Dear list members,

We are pleased to announce the release of LiveCode 9.5.1 STABLE.

** Note 9.5.1 STABLE is the last planned release in the 9.5.x series **

Getting the Release
===
You can get the release at https://downloads.livecode.com/livecode/ or via
the automatic updater.


Release Contents


LiveCode 9.5.1 STABLE contains more than 20 bugfixes and improvements
compared to the previous (9.5.0) STABLE version, including the long
standing crash-when-debugging issue, originally fixed in 9.0.5.


Notes:

- Building with Xcode 11.x is *not* supported in LC 9.5.1, but in any case,
you do NOT need to build your standalone with Xcode 11+ to support
deployment to iOS 13+ devices. You can still use Xcode 10.1 to build the
standalone app, and it will continue to run on iOS 13+ devices.


The full release notes are available from:
http://downloads.livecode.com/livecode/9_5_1/LiveCodeNotes-9_5_1.pdf


Feedback

Please report any bugs encountered on our BugZilla at
http://quality.livecode.com/


Have fun!
The LiveCode Team
--
___
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: get URL problems

[Matthias Rebbe via use-livecode]

Hi Hugh,

i cannot replicate this here with LC 9.5.0 Business on Mac. When i run your 
script, tJSON shows the returned data.

What version of LC are you using?

Regards,

Matthias



> Am 16.12.2019 um 10:54 schrieb FlexibleLearning.com via use-livecode 
> :
> 
> put
> "https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=MSFT&ap 
> 
> ikey=demo" into tURL
> launch url tURL --| Works fine, page loads entirely as expected in default
> web browser
> get url tURL --| Returns empty, nada, not a sausage
> put it into tJSON 

___
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

get URL problems

[FlexibleLearning.com via use-livecode]

Why can I 'launch' this url but not 'get' it?

put
"https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=MSFT&ap
ikey=demo" into tURL
launch url tURL --| Works fine, page loads entirely as expected in default
web browser
get url tURL --| Returns empty, nada, not a sausage
put it into tJSON 


I am using libUrl v1.1.6 300506


Thanks peeps!

Hugh


___
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