OT Livecode and Intego Virus Barrier
matthias_livecode_150811 at m-r-d.de
Fri May 27 10:19:02 CEST 2016
so there´s no need for me to file a bug, right?
Or should i report it? I do not to bother the team with unnecessary things.
> Am 27.05.2016 um 09:28 schrieb Fraser Gordon <fraser.gordon at livecode.com>:
> On 27/05/16 02:39, Lyn Teyla wrote:
>> 2. The method used by LiveCode to write to LiveCodeToolsLog.txt (presumably multiple times) might not be ideal. Could be a "write to file" vs "put into url" issue.
>> Better yet, perhaps the writing to this log file should not be performed by default, unless a debug setting is set via Preferences.
> The main purpose of the IDE log file is diagnosing problems with the IDE starting up. Unfortunately, this means that it can't be toggled by a preference because if the IDE is failing, you can't toggle the preference.
> Because of this purpose, the way the file is written is very conservative - every time a line is logged, the file is opened, the line is appended and then the file is closed again. This ensures that in the event of an engine crash, the logging data is not lost.
> One thing that is definitely worth considering is deleting the current contents of the file when the IDE starts up rather than preserving the content indefinitely.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode