Re: Opening a stack without a .livecode extension

2016-09-29 Thread Richard Gaskin
Graham Samuel wrote: > Thanks Richard. You're right (of course!), it’s a path problem. But > it’s a pretty subtle one, since I obtained the path by executing > put specialFolderPath("preferences") & “/my preferences" into > tPrefsPath > > Which should have given me a cast iron result. Turns out

Re: Opening a stack without a .livecode extension

2016-09-29 Thread Graham Samuel
Thanks Richard. You're right (of course!), it’s a path problem. But it’s a pretty subtle one, since I obtained the path by executing put specialFolderPath("preferences") & “/my preferences" into tPrefsPath Which should have given me a cast iron result. Turns out that this produces a path with

Re: Opening a stack without a .livecode extension

2016-09-29 Thread Richard Gaskin
Graham wrote: > I’ve got a preferences stack which is called something like “my > preferences”. It’s not called “my preferences.livecode”. It’s a > mainstack, not a substack of any other. The path to the stack is > of the form > > /Users/Graham/Library/Preferences/my preferences > > If I put the

Opening a stack without a .livecode extension

2016-09-29 Thread Graham Samuel
I’ve got a preferences stack which is called something like “my preferences”. It’s not called “my preferences.livecode”. It’s a mainstack, not a substack of any other. The path to the stack is of the form /Users/Graham/Library/Preferences/my preferences If I put the path to the stack in a