Closed GoogleCodeExporter closed 9 years ago
(Sorry, I would change the title to reflect the actual bug, but don't see how
to do
that here.)
Original comment by brandyn....@gmail.com
on 14 Sep 2009 at 1:58
It'll require a separate SetContactListener in the way I've done the userdata
(see
[http://code.google.com/p/pybox2d/source/browse/trunk/Box2D/Box2D_userdata.i
here])
-- Ignoring the original, using a custom __del__ (with a decref) in b2World so
that
objects containing its reference will destruct properly.
Same applies to debug draw, boundary, and destruction listeners.
I've always known about the issue, it was just never high on the list as its
fix is
simple -- store it. :) Thanks for the report in any case; I'll probably get
around to
it eventually.
Original comment by sir...@gmail.com
on 14 Sep 2009 at 2:14
Yup, easy workaround. A quick "fix" would be to just document the bug.
Would this be the best place?
http://www.box2d.org/wiki/index.php?title=Python_Manual#Contact_Listener
(I don't seem to have edit access; not sure what it takes to create an account
there
and all that -- if it's easy for you...) And/or I suppose in the doc string for
SetContactListener.
All in all, pybox2d is working great btw...
Original comment by brandyn....@gmail.com
on 14 Sep 2009 at 4:18
Fixed (or at least an attempted fix) in the bleeding edge 2.1.0 version. Don't
intend
on fixing this for 2.0.2.
Original comment by sir...@gmail.com
on 11 Jan 2010 at 2:38
Original issue reported on code.google.com by
brandyn....@gmail.com
on 14 Sep 2009 at 1:56