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 No
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
appro
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 certai
Malte,
I have no idea, but I am running the IDE here and I have two of those
files in that folder. Since they are named PID, I suspect that they
somehow hold information about the running process ID or something similar.
om om
andre
On 11/12/2018 9:23 AM, Malte Pfaff-Brill via use-livecode
Hi,
Does anybody know what causes files to be created in
C:\Users\*\AppData\Local\._LiveCode_\ for a standalone under Windows 7? Does
this have something to do with the creation of UUIDs? Can the creation of those
files be avoided?
Cheers!
Malte
__
