Bob Sneidar wrote:
> Yes, with Windows 10, there is a feature called Sandboxing, where even
> if your logged in user has write permissions to where the stack is
> saving, you will still not be able to write there. Program Files is a
> great example. The solution is not to save stacks. Stacks should not
> be the place you save information.
LiveCode stack files are a format; the file path is the location.
While it's often useful to separate UI from code, sometimes stack files
make a really good storage format.
Windows does not care about the internal format of a file, only where
it's saved.
Wherever you can store any binary file, you should be able to store
stack files.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
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
