[Bf-python] data corruption

[Campbell Barton]

Has this been fixed in the CVS? I vcant get the logs right now, its a 
fairly major bug- can loose your work and olny find out on resave.
- Cam
Ken Hughes wrote:
> Martin Poirier wrote:
>>
>> --- "Gilbert, Joseph T." <jgilbert at tigr.ORG> wrote:
>>
>>
>>> I am not sure if objects behave the same way as
>>> other data. If an
>>> armature data block has an id.us of 0 it's not freed
>>> (because we set it
>>> to zero manually when the object is created). Maybe
>>> what's happening is
>>> that when a user manually deletes an object from a
>>> scene somewhere the
>>> free() code for that object is called?
>>
>>
>> Ken mentionned that in his previous mail, Objects and
>> Scenes are the only two blender types which are
>> automaticly freed from memory when their user count
>> reaches zero.
>
> Yeah, I assume it's free_libblock_us() which is being called, because 
> it explicitly check for an object reading a use count of zero and 
> deleting it.
>
>> For all the others, BPY wouldn't *need* to increase
>> the users on binding and decrease on destroy, but it
>> would be safer nonetheless to do it, I think.
>
> Ken
> _______________________________________________
> Bf-python mailing list
> Bf-python at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-python
>


-- 
Campbell J Barton

133 Hope Street
Geelong West, Victoria 3218 Australia

URL:    http://www.metavr.com
e-mail: cbarton at metavr.com
phone: AU (03) 5229 0241