windows defender issues? & other AV issues
bobsneidar at iotecdigital.com
Tue Jan 15 16:54:17 CET 2019
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. Think of them as more like web forms.
I learned this the hard way. Instead you should save settings and such in a "safe" location, either in a database or else in some kind of settings file. I have a whole system for this. I arrayEncode an array I use runtime for my settings and save it to disk each time a setting changes.
> On Jan 15, 2019, at 01:59 , R.H. via use-livecode <use-livecode at lists.runrev.com> wrote:
> Failed saving onWindows 10 (all latest versions of LiveCode)
> I am talking about a compiled business related stack (small compiled
> splash, main stack not compiled in a resource folder and various resources)
> that goes to clients.
> Some of my clients experience that the main stack is not saving and will
> leave two files in a state that does not allow to reopen them again. One of
> the files is renamed with a tilde character "~" at the end of the filename.
> This is the file "in progress" to be saved from file A to B and when the
> saving was successful, the old file is removed.
More information about the use-livecode