Re: Pingu stuck and collision code

[Ingo Ruhnke]

David Philippi <address@hidden> writes:

> 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).

What we need isn't really just plain walker code, but more generic
pixel-terrain traversing code, but as this would need to be quite
flexible (should handle climber, slider, skater, walker and
upsite-down-walker) I don't really now if it could improve the
situation much. We would also need a virtual "bool collide()" and
things like that. Simply fixing the few remaining bugs could be a lot
easier and wouldn't break everything.

-- 
WWW:      http://pingus.seul.org/~grumbel/ 
Games:    http://pingus.seul.org/~grumbel/gamedesigns/
JabberID: address@hidden 
ICQ:      59461927