[Bf-python] Dreaded blue dots

Campbell Barton cbarton at metavr.com
Wed Sep 20 13:35:44 CEST 2006


Martin Poirier wrote:
> --- Campbell Barton <cbarton at metavr.com> wrote:
>
>   
>> Chris Want wrote:
>>     
>>> Does anybody know why after a script failing,
>>>       
>> quite often
>>     
>>> the center point of an object that the script was
>>>       
>> acting
>>     
>>> on will be blue in color? Is this a sign that the
>>>       
>> object
>>     
>>> and or scene database has become corrupted?
>>>       
>> Anybody
>>     
>>> else notice this?
>>>       
>> Blue dot means the object has more then one user
>> so if an objects in more then 1 scene for eg..
>>
>>
>> Python Objects are now counted as a user (changed a
>> while ago-)
>> somehow the Object isnt decrefed. Iv had this a few
>> times but not found 
>> it to mess up the user count in the long run.
>> Though its worth seeing why objects variables arnt 
>> decreffed.
>>     
>
> I guess it would depend on where the BPy object is
> stored (namespace-wise). Are we still sharing the
> global namespace between scripts? If that's the case,
> that could be the culprit.
>
> Martin
>   
Blender.* can be shared between  scripts. I dont think globals are 
shared as in "global foobar"

I was thinking  maybe the python API could be a Fake user, would need 
some trick so it knows not no unset Objects that were originaly fake 
users on deallocations.

Tried making 1000000's pyObject-objects to  mess the user count up, 
while the databrowser displayed negative values somtimes. It didnt mess 
up the internals when saving or after the Python decrefed the variables.

-- 
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



More information about the Bf-python mailing list