Hi,
I've had to correct a Lazarus startup problem for 2 of my collegae.
The cause was that the editormacros.xml and editormacroscript.xml files were
filled with zero bytes.
How this came to be, I do not know. I do know the consequence:
The IDE completely failed to start after that.
The solution was to start with a new empty settings directory.
I found out which files were to blame by copying the old files one by one in
the new directory, and
restarting lazarus after each one, to see when the problem reappeared.
My collegae never would have been able to solve this problem by themselves,
leaving them in quite an awkward position: an unusable IDE.
Might I suggest that the IDE tries to recover more gracefully when one of it's
config files is corrupted ?
Showing an error box to alert the user is OK, but it should try to rename the offending file to something sane,
and start with an 'empty' file.
Depending on which file it is, the working of Lazarus may be more or less
impeded, but at least it starts.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
