From 96780fc21f2d4b0f766ea5c32f33e11b0e343f29 Mon Sep 17 00:00:00 2001 From: Justin Butler Date: Tue, 2 May 2006 03:25:24 +0000 Subject: [PATCH] set object location to 0,0 when going into the cache, instead of None,None since when the object is pulled back out of the cache, None,None were not clearing out the old location. --- direct/src/distributed/DistributedObject.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/direct/src/distributed/DistributedObject.py b/direct/src/distributed/DistributedObject.py index 5fd8790301..35a812961d 100644 --- a/direct/src/distributed/DistributedObject.py +++ b/direct/src/distributed/DistributedObject.py @@ -183,7 +183,7 @@ class DistributedObject(DistributedObjectBase): self.activeState = ESDisabled self.__callbacks = {} #self.cr.deleteObjectLocation(self.doId, self.parentId, self.zoneId) - self.setLocation(None, None) + self.setLocation(0,0) # TODO: disable my children def isDisabled(self): @@ -383,7 +383,7 @@ class DistributedObject(DistributedObjectBase): self.cr.sendSetLocation(self.doId, parentId, zoneId) def setLocation(self, parentId, zoneId): - self.cr.storeObjectLocation(self.doId, parentId, zoneId) + self.cr.storeObjectLocation(self.doId, parentId, zoneId, self) def getLocation(self): try: