.PID file in C:\Users\*\AppData\Local\._LiveCode_\

[Monte Goulding]

This is not something I’ve looked at before but it appears the files should be being cleaned up at the end of the session. I guess if LiveCode writing this file is a particular issue for you then you could put in a feature request to toggle relaunch support in the standalone builder.

> On 12 Nov 2018, at 9:19 pm, Andre Alves Garzia via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Malte,
> 
> Found it in the source:
> 
> https://github.com/livecode/livecode/blob/d780d79e800afd65897631f840296075ff6573e9/engine/src/w32relaunch.cpp#L310
> 
> As I suspected, it is related to the running process. We still need to hear from the mothership about it but files in AppData/Local should be approved by your clients right? That is a common folder where apps write support and temporary stuff.
> 
> Cheers
> 
> andre
> 
> 
> On 11/12/2018 10:01 AM, Malte Pfaff-Brill via use-livecode wrote:
>> Thanks Andre!
>> 
>> I guess I will have to wait for someone from the mothership to join in then. :-/
>> I am currently trying to get the OSS project I am stewarding approved by a governmental agency and those files might be a showstopper, as I am not supposed to leave traces in the system, besides certain specified folders where I may get permission to write files.
>> 
>> Cheers!
>> 
>> Malte
>> 
>> 
>> _______________________________________________
>> 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