Thanks for the info! I hope you solve the problem. JB
> On Dec 16, 2019, at 7:55 AM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > 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@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 > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
