JeLlyFish.software at gmx.net
Sat Oct 4 19:34:29 CEST 2008
Micha Nelissen wrote:
> Vinzent Höfler wrote:
>> Often, after a first install, the local config does not exist yet (or
>> the user may have deleted it), so your proposed approach would
>> completely disable the local config then, because without the proper
> No, when saving you always save to the local config file, because most
> of the time you're not allowed to write to the global one.
Yes, but your proposal would never return the file name of a local
config if it doesn't exist in the first place, so how would an
application find out where it's supposed to create it?
> Loading is more common than saving, that's the use case I am talking about.
Well, and that use case usually involves loading *both* files, first the
global settings and then optionally tweaking it with a user specific
configuration. For those cases your approach wouldn't work neither.
More information about the fpc-devel