Bug in vizproximity.Manager.removeSensor
When moving our code from using hotspots to vizproximity I seem to have discovered a bug in this module (both already available in Vizard4). The method vizproximity.Manager.getActiveSensors() can return sensors which have already been deleted through vizproximity.Manager.removeSensor(). Which, when you have the need to add and remove frequently, leads to accumulation of (not available) sensors in the active list of a target.
I took the liberty to check the module and found this: the update routine adds a set of sensors that are currently triggered to each target and stores this in the self._target dictionary: Code:
def update(self): Code:
def removeSensor(self,sensor): |
Thanks for taking the time to report this bug and also find a fix!
|
Could you please include this fix in a future release of both 4 and 5? I have multiple machines on which I run Vizard and I don't want to fix this error on all of them...
Thanks! |
As far as I have checked, the patch is included in the final release of Vizard5.
If Vizard4 will receive another patch - I don't think so. But that's up to WorldViz, of course. Best Regards, Walter |
All times are GMT -7. The time now is 07:17 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Copyright 2002-2023 WorldViz LLC