Standalones and the defaultFolder
Bob Sneidar
bobsneidar at iotecdigital.com
Mon Dec 16 10:55:14 EST 2019
Thanks JB. Getting and setting the default folder was not the issue. The issue is that in a wondows standalone, a stack in the same folder as the executable could not be opened by script eg. open stack "Devices". This seems to be a new development, as I am fairly certain this worked fine in the past. ALL stack files in a standalone ought to be discoverable no matter what the defaultFolder is.
Bob S
> On Dec 14, 2019, at 04:27 , JB via use-livecode <use-livecode at lists.runrev.com> wrote:
>
> I am not using Windows or the version of Livecode you are
> using so I am not testing this but when it comes to using
> paths you might want to make sure what path is being
> provided.
>
> If the path returned includes a file name then it might
> not work properly for listing that directory because it
> is trying to list the directory of the file name instead
> of the folder the file is in.
>
> This behavior could also cause your program to not
> see something making you think the default folder
> is not working properly when it might be the path
> the default folder is using ends with the file name.
>
> JB
More information about the use-livecode
mailing list