get URL problems

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

Re: get URL problems

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

[ANN] Release 9.5.1

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.

Re: Standalones and the defaultFolder

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,

Re: get URL problems

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 lau

Re: Standalones and the defaultFolder

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

Re: Standalones and the defaultFolder

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 co

Re: Standalones and the defaultFolder

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

Re: Standalones and the defaultFolder

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 chan

[ANN] This Week in LiveCode 206

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

Re: Standalones and the defaultFolder

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 t

Something wrong with LiveCode 9.5.1

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

Re: Something wrong with LiveCode 9.5.1

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

Re: Something wrong with LiveCode 9.5.1

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 loc

Re: Something wrong with LiveCode 9.5.1

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 t

Re: Something wrong with LiveCode 9.5.1

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

Re: Something wrong with LiveCode 9.5.1

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.

Re: Something wrong with LiveCode 9.5.1

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 com

Re: Something wrong with LiveCode 9.5.1

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 Sier

Re: Something wrong with LiveCode 9.5.1

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 wa

Re: Something wrong with LiveCode 9.5.1

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

Re: Standalones and the defaultFolder

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 ma