smilr wrote:So?
I guess you missed my point. We're not going to take a very minor problem and work to turn it into a larger one for an insignificant benefit.
smilr wrote:Copy the contents out to a new folder you create - then delete the old one - or, if there is an error during an attempted name-change/create/delete, alert the user about it and continue operating with the prefs inside the adium 2 folder.
Scenario: User downloads a beta of Adium .9 and opens it while .8 is running, then decides to wait until .9 is finished and closes it.
1) .9 Copies the preferences to a new location and deletes the old.
2) .8 Writes back preferences as they are modified, but not all preferences are modified every session.
3) User quits Adium and goes to sleep, comes back tomorrow to find that a large portion of their preferences have been deleted.
You make it out like this is a simple change, it is not. Your code just deleted my preferences and now I'm angry.
smilr wrote:It may be a hassle - but sooner or later this transition should happen, better to think about it early and not be caught blindsided by it.
As I said, it WILL happen, but only when it becomes necessary. We have thought about it, even wrote the code for it only to decide that it wasn't worth the risks for such an insignificant benefit.