Re: Pingu stuck and collision code

[David Philippi]

On Friday 13 September 2002 21:31, Ingo Ruhnke wrote:
> We should really unify the collision and walk code a bit, moving a
> pingu 2 pixels or more at a time without error checking can be a good
> way to create bugs. The slider actions currently suffers a similar
> problem.

What about a common walk code in PinguAction that gets called from every 
action after they did performed specific modifications to their surrounding 
if any. This means that a walker would just call the derived method while a 
basher would first remove a piece of wall and then call the walking code.
I guess the common walking code is quite similar to the code of the current 
walker and should probably return a enum { collission, falling, ? } which 
must be interpreted in the correct way by the actions (e.g. a digger won't 
change to faller if it's falling).

Bye David