[Bf-committers] Blender user config files get lost on new release...

[Ton Roosendaal]

Hi,

I would simply on startup - provided the user directory doesn't exist  
yet, make a full copy by default and not bother users with such non- 
decisions. If Blender 2.55 was working fine, so should 2.56  
automatically.

Compatibility is a great feature... maybe a 2.5 directory would have  
been nicer, and keep all settings compliant for a longer while.

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

On 2 Jan, 2011, at 8:08, Wahooney wrote:

> You could also have custom/modified scripts that need to be copied
> across, this could also be (optionally) handled in that button press.
>
> On 2011/01/02 12:39 AM, Matt Ebb wrote:
>> On Sun, Jan 2, 2011 at 4:20 AM, Ton Roosendaal<ton at blender.org>   
>> wrote:
>>> Hi,
>>>
>>> Although I see the use of having a user config based on release
>>> number, it means these files get not found when you upgrade to 2.56.
>>>
>>> At least here for me in OSX... I thought Campbell mentioned this  
>>> gets
>>> copied over, but I can't find this code. I assume it should work  
>>> like
>>> backwards checking for all 2.5x directories?
>> Or at the least it would be good to have a button in splash screen  
>> etc
>> that would appear in such a situation 'migrate old user settings' or
>> something like that.
>>
>> Matt
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers