[Blog] Script Only Stacks
bleiler at buffalo.edu
Thu Mar 3 13:24:13 EST 2016
I gave that a try and I still get the same message. My attempts to create them from scratch were saved as UTF-8 and I’ve tried all the other options in TextEdit as well. I have noticed that if I open a functioning script only stack in ATOM it is identified as UTF-8.
> On Mar 3, 2016, at 1:12 PM, Peter TB Brett <peter.brett at livecode.com> wrote:
> On 03/03/2016 17:48, Tim Bleiler wrote:
>> In the blog post, Mark states that "The fact that script only stack files really are just text files is really important! It means you can edit and create them in any text editor you choose, and use any text based processing tool on them…”
>> I’ve been trying to work with script only stacks on Mac OS X 10.11 for a few weeks now, at least since Livecode version 8 dp12. If I open one up in TextEdit and save it, Livecode gives me the error message: “Unable to open stack: File is not a stack”. The only way to recover the script has been to copy and paste it from the text editor into a new script only stack script. Additionally, I’ve never been able to create one in a text editor from scratch without getting the same error message from Livecode when I try to open it. I figure I must be doing something wrong because with the team using these all the time I don’t see how they wouldn’t have run into this. Any suggestions?
> The only thing I can think of to suggest is to make sure that your editor is saving the file as UTF-16 text.
> Usually script-only stacks start with a UTF-16 byte order mark.
> Dr Peter Brett <peter.brett at livecode.com>
> LiveCode Open Source Team
> LiveCode 2016 Conference https://livecode.com/edinburgh-2016/
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode