best way to open a script-only library stack?

--When you start using a script-only stack, LC creates a temporary hidden --stack in RAM and assigns the script to it. It's there but not visible. Ah ha... now at least I don't feel silly for not finding it. And it is in the Project Browser too – I may have opened it from there once actually, a

best way to open a script-only library stack?

I'm just getting started with the idea of a library stack for scripts, and have a dopey question: what's the best way to edit the library as I work on the project? I've created a script-only stack and included start using stack "myScriptStack.livecodescript" in the preOpenStack handler of my

filename in standalones for Mac - changed recently?

I'll file this under "things I wish I'd known about a few years ago"... put specialfolderpath("resources")& "/media/" into gMediaPath More elegant, change-proof, and works. Thanks Klaus! :) -Curt -- Sent from Postbox

filename in standalones for Mac - changed recently?

The other day when firing up TextWrangler, I saw the message that Apple now shows once when opening a 32bit app – that it should be updated (for 64bit). Which got me thinking about older Livecode projects. A few years ago I did a series of modules for a client (using Livecode 7) that included

script/engine broken when moved to 64bit server at JaguarPC

I've received this from JaguarPC: [Sun Sep 10 01:51:36.334093 2017] [cgid:error] [pid 22868:tid 139689650484992] [client 69.73.180.11:50074] End of script output before headers: keygentest.cgi That occurs when a

re: script/engine broken when moved to 64bit server at JaguarPC

JaguarPC hasn't answered the question about dependencies directly, though they did pass on this: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory ..which suggests a dependency issue, I guess? But they've also said Correct, the initial error was due to using a 32bit compil

re: script/engine broken when moved to 64bit server at JaguarPC

It's the 500 internal server error. I'm pretty - er, very new to troubleshooting on a server. I don't have SSH access. Is there a way to get a list of the dependencies of the 32bit and 64bit engines that I could forward to JaguarPC? I know someone else has the 32bit engine working on JaguarPC,

script/engine broken when moved to 64bit server at JaguarPC

For several years I've had a system on JaguarPC involving a simple script that calls Livecode server, with script and server engine in the cgi-bin folder. Last weekend we were moved to 'sagitarius,' a 64bit server, and our system has broken. I tried uploading the 64bit version (from LiveCodeS