Re: [pygame] Collision Resolver module

[sjbrown@xxxxxxxxx]

I'm not sure what tutorial you're referring to.

What this collision_resolver module does that the provided tools do not do
is detect collisions that happened inside the hexagon that the rect
travelled through, and provide an easy way to resolve the collisions so that
the moving rect can be "blocked" by the colliding rects.

For a simple example, consider what happens when a rect is falling downward
and right in a platformer such that it will collide with a platform in the
next timestep.  what if the start and end rect don't actually intersect the
platform, but the hexagon does intersect the platform?  This can occur when
the falling rect is going near the edge of the platform.

You should download and run the example.  It's pretty simple.


> On Jan 1, 2008 7:49 PM,  <sjbrown@xxxxxxxxx> wrote:
>> Pygame should aspire to providing a very rich (while being consistent,
>> lean,
>> and elegant) set of tools.
>>
>
> I'm not a smart pygame user yet so my opinion can be very poor, but
> what I quoted here is true, and important. This is true for all engine
> in general, not only pygame.
> I've not tested the example and the library that generated this
> thread, but for what I see and tryed from the Pygame base tutorial, a
> Sprite collision is already present.
> The tutorial itself says "...but probably this will be enough for you use".
>
> So you are talking here of something that pygame already do... but not well?
>
>