search

ratalaika / angel-engine

Automatically exported from code.google.com/p/angel-engine
0 stars 0 forks source link

Collision Rework #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The current system for handling and reporting collisions is
1. Not terribly robust due to changes in the way Box2D reports collisions
from version 1 to version 2. 
2. A bit silly with the way it generates messages that rely on knowing the
object's name. 
3. Doesn't mesh well with the old CollisionResponse system. 

In short, collisions need a revamp.

Original issue reported on code.google.com by lieseg...@gmail.com on 4 Feb 2009 at 8:56

GoogleCodeExporter commented 9 years ago

Original comment by lieseg...@gmail.com on 10 Feb 2009 at 12:04

GoogleCodeExporter commented 9 years ago

Original comment by lieseg...@gmail.com on 10 Feb 2009 at 12:05

GoogleCodeExporter commented 9 years ago 
We at least need to figure out what's causing collisions to not always get 
reported
before 2.0 is finalized.

Original comment by lieseg...@gmail.com on 10 Feb 2009 at 12:46

GoogleCodeExporter commented 9 years ago 
Moving back to 2.5, since the "collisions not getting reported" bug was simply 
me
forgetting how I had designed one of the DemoScreens. Better comments fixed the
problem. :-)

Original comment by lieseg...@gmail.com on 10 Feb 2009 at 2:27

GoogleCodeExporter commented 9 years ago 
Closing this until someone complains that their collisions don't work.

Original comment by lieseg...@gmail.com on 3 Jul 2010 at 1:27