LiveCode Forums

But, I am like a tree: my bark is worse than my bite!

...and he doesn't leave until spring.

What is the number of hours for?

I'm guessing the next number is 48.
But that numeric string occurs at the 182965th position in pi.
http://www.angio.net/pi/

Oooo... I take back the part about it not crashing LC.
That's pretty dramatic.
Luckily I didn't have anything else open at the time.

FWIW I have *never* gotten the Browser widget to work on linux. At least it no longer crashes LC when it doesn't work.

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

/sigh... I submitted a fix for this almost a year ago. If anyone wants to pick this up and resubmit it, feel free.

https://github.com/livecode/livecode/pull/6496

Alejandro- that chromium discussion link is about supporting HTTP/0.9 long-term, while the server in question here is using HTTP/1.0. But the shoutcast audio stream content is audio/x-scpls in spite of the web site saying that it's audio/mpeg. So unless the target computer can handle this type of st...

Most handle it by writing interfaces to OS APIs, just as we can do in LC.

Interfacing to OS APIs requires at least proficiency in LCB, and at worst requires writing external libraries in something closer to the metal. It's not a simple matter of scripting

export mySound as "mp3"

Looking forward to the March meeting on the 7th to tie in with SCaLE.

I would consider this a bug in LCB JSON formatting. The code in the JSONExport handler in json.lcb is public handler JsonExport(in pValue as optional any) returns String if pValue is a string then return JsonExportString(pValue) else if pValue is a number then return JsonExportNumber(pValue) else if...

Ah, I see - you're doing an import first, and then an export. Yes, LC is internally flagging the input value as numeric rather than performing a default string conversion. Interestingly, examining the resulting internal arrays shows no difference. It's JSONExport that's doing the internal conversion...

http://www.todayifoundout.com/index.php ... t-of-time/

TIL - thanks for that. Although I admit to being partial to the quantum of time being the time required for light to travel the Planck length.

Well, neither JSONImport nor JSONexport are doing number conversion, so that's not where your problem lies. Here's a simple test that shows that the result of exporting and importing gives identical arrays. on mouseUp pMouseButton local tJSON local tJSONArray, tOutputArray put 7873356 into tJSONArra...

Same.
And I think the import/export facility will fall out naturally when this happens.

BTW, I submitted a PR to fix the linux backdrop thing back in April. If anyone wants to pick it up and run with it, please do - it's basically a one-line fix (two lines if you want to be pedantic about it).

https://github.com/livecode/livecode/pull/6496

Happily, Chrome 71 fixes this vulnerability. Thanks to Tencent for finding the bug.

You can test your browser at https://worthdoingbadly.com/sqlitebug/

Yah, that's the one thing that bugs me about python programming. But a good IDE will enforce proper indentation to help keep you out of trouble. ... and don't forget ruby's spaceship operator (<=>). It's actually a very useful operator, and one that would help solve a lot of the numeric/string compa...