diff options
author | Bertram <bertram@cegetel.net> | 2009-09-22 00:24:33 +0200 |
---|---|---|
committer | Bertram <bertram@cegetel.net> | 2009-09-22 00:24:33 +0200 |
commit | bf6e1331941daecb3c3ff12c3b86457899042953 (patch) | |
tree | 35c08ff4c09c602c2b22be2a9dba0b6cb9e1d9a5 /src/gui/linkhandler.h | |
parent | 1aa425bb4c846c978712410de311181c84a1d097 (diff) | |
download | mana-client-bf6e1331941daecb3c3ff12c3b86457899042953.tar.gz mana-client-bf6e1331941daecb3c3ff12c3b86457899042953.tar.bz2 mana-client-bf6e1331941daecb3c3ff12c3b86457899042953.tar.xz mana-client-bf6e1331941daecb3c3ff12c3b86457899042953.zip |
Mostly fixed the mouse movement in TMWserv client.
The only case left in mouse movement is that the client doesn't check
for walkability of the destination point when you click on a unwalkable point.
Let me explain this NASTY bug:
The bug remained in the Being::SetDestination() function,
when recalculating the path from tiles to pixels.
The changeX and changeY variables went crazy when (endX - startX) gave a negative value.
That why the given path became random, and the player went anywhere.
This didn't happened to monsters, NPCs, and when walking using the keyboard
because the patnodes system isn't used for movement up to 1 tile at a time.
I removed some dead code (in viewpoint.cpp), made the keyboard navigation a little
bit more bearable, and fixed this client bug.
Now, I'll be up to finish fixing the movement system using mouse (What's remaining is a joke
next to what I had to do to discover this...),
and I'll look at a third time to the keyboard system which is a bit raw, just for now...
Regards,
P.S.: Kage, I'd like to get a three-cheese pizza!
Diffstat (limited to 'src/gui/linkhandler.h')
0 files changed, 0 insertions, 0 deletions