LiveCode Forums

PS just found the link in the Dictionary to Tech Strategies, so I asked them too.

I have a simple stack in 9.6.9-rc-2 that does GET and POST to https://api.getmaintainx.com/v1/ and the standalone works just fine in OSX/monterey and Windows 10, but it fails on Windows 7 with the error tsneterr: (35) schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326...

Indeed. For people building human machine interface control systems - that's me - it's too bad there's no rpi engine that actually works, because LC + rpi would make a great industrial control station. Writing to a field repeatedly leaks memory, and if you're writing clock or positional data at high...

Compiling 8.1.10 from source: looking for source code to ./prebuilt for 8.1.10, e.g. so I can build libcustomcrypto.a and libcustomssl.a. Also wondering about libiucle.a and libiculx.a in prebuilt/lib, but not in my build of ICU. I get pretty far into the armv6hf 8.1.10 build before hitting this pro...

Thanks, Richard. I was just in the process of deleting my whole post out of frustration.

I've been working on building the standalone for 9.5.1 using the gnu cross compiler. It's not easy!

The memory leak I'm talking about is on the Raspberry Pi 4 OS with LC 6.5.1 standalone, and not some other platform. It doesn't matter if you wait 10 milliseconds, or send in 10 milliseconds, or both wait and send in 10 milliseconds, or repeat forever, or what you're writing, or the options for buil...

It doesn't matter what you put in the field - I just gave the long time or the long seconds so you could see the field change. On Raspberry Pi 4 running the Raspberry Pi OS, LC 6.5.1 memory will go up until it crashes.

It doesn't matter if you use a repeat forever or send: memory still leaks. The only thing that prevents the leak is to make the field or button invisible. You will notice the leak if your application continually changes half a dozen fields at 10Hz, and it will really eat memory if you let it run ful...

Unfortunately, 6.5.1 has a memory leak on my RPi4. Just repeatedly put the long time into a a field or button label, i.e. a clock field, at full bore, and you'll see memory creep up in top, and eventually end with a crash. Building Pi standalone programs isn't going to be easy, whether built nativel...

6.5.1 runs on the RPi 4! This is great for my work, because the 7 and 8 series were broken for sockets (sockets were fixed partway through 8 after I submitted the bug report.) I know there are a few bugs left in 6.5.1, but it is a great desktop release for machines that support 32-bit programs. I'm ...

This has been confirmed as a bug 20507, introduced in LC 7. I guess I'm the only one on the planet using the "for n" clause. The latest version I can use for Linux/OS X/Windows is 6.1.1.

I get the same issue with 8.1.7. I think this problem has been with all of 8, and possibly 7. Thanks for the suggestion. I have a long history of finding socket bugs - the biggest doozy was in a Linux engine, where a socket timeout would cause the graphics to freeze unless you wiggled the mouse.

I tried adding "for 1 char" but that makes no difference, i.e. in 6.1.1 this sample code really reads just 1 character, and in 8 it now returns more than 1 character if available. The "until" form *does* work - the read will correctly return up to the match character. For example, "telnet localhost ...

Thinking it would a cinch to upgrade from 6.1.1 to 8.1.6, I am having trouble with sockets again. Maybe I'm doing something wrong, but in 8.1.6 running in Sierra 10.12.6, trying to read just 1 character doesn't seem to work like it does in 6.1.1. Either I'm an idiot (possible) or nobody is using soc...

Don't know if this is the right forum, but I decided to try Community 7.0 RC1, coming from 6.1.1 and 6.1.3. Standalones for all 3 platforms went from 3Mb to about 13Mb, and performance went from snappy fast to sluggish screen updates in Windows 7 and OS X. What am I doing wrong? -John