windows defender issues? & other AV issues

[J. Landman Gay]

The best folder to write to on mobile is "documents". Both iOS and 
Android are sandboxed and disallow writing to either "engine" or 
"resources".

On 1/15/19 12:04 PM, JJS via use-livecode wrote:
> You could also use "home" as it works on 3 desktop platforms and iOs. 
> Linux does not have a "support". and Android uses "Engine"
> 
> 
> Op 15-1-2019 om 17:38 schreef Matthias Rebbe via use-livecode:
>> There should be no problem to copy/write/save a stack to the folder 
>> AppData . This is the recommended place if your app needs to write 
>> data to disk. It can be access using specialfolderpath("Support") or 
>> specialfolderpath(26).
>>
>> Or has this really changed in Windows 10?
>>
>> Matthias Rebbe
>>
>> free tools for Livecoders:
>> https://instamaker.dermattes.de <https://instamaker.dermattes.de/>
>> https://winsignhelper.dermattes.de <https://winsignhelper.dermattes.de/>
>>
>>> Am 15.01.2019 um 16:54 schrieb Bob Sneidar via use-livecode 
>>> <use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>:
>>>
>>> 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.
>>>
>>> Bob S
>>>
>>>
>>>> On Jan 15, 2019, at 01:59 , R.H. via use-livecode 
>>>> <use-livecode at lists.runrev.com 
>>>> <mailto: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.
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com <mailto:use-livecode at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com