Bug 231591 - bug in collision detection - can move out of the level
Summary: bug in collision detection - can move out of the level
Status: RESOLVED DUPLICATE of bug 181081
Alias: None
Product: kapman
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Thomas Gallinari
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-21 22:17 UTC by Peter Barth
Modified: 2014-09-05 15:57 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot illustrating the problem (67.39 KB, image/png)
2010-03-21 22:18 UTC, Peter Barth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Barth 2010-03-21 22:17:44 UTC
Version:            (using KDE 4.3.5)
Compiler:          gcc 4.3.4 
OS:                Linux
Installed from:    Gentoo Packages

Let's assume you're running east direction to a corner of the field board which makes a turn right (i.e. down). If you reached that corner really quickly move the button combination "down" and "up" and you will magically go through the level borders.

To illustrate that I made a screenshot where I left the game board. Though you can go through any wall that lies within a corner with that "trick" ;)
Comment 1 Peter Barth 2010-03-21 22:18:41 UTC
Created attachment 41819 [details]
Screenshot illustrating the problem
Comment 2 Stefan Majewsky 2011-01-01 22:00:19 UTC
Is this still reproducible? I tried it with the 4.6 version here, but cannot reproduce, though this might have to do with my inferior keyboard skills. ;-)
Comment 3 Peter Barth 2011-01-17 19:27:08 UTC
Kapman Version 1.0.0 Unter KDE 4.4.6 (KDE 4.4.5)

I'm still able to walk through walls ;)
Comment 4 Peter Barth 2011-09-04 22:04:01 UTC
Version 1.0.1 - KDE 4.6.5

Still can leave the game board, though what's new: I don't manage to get back :)
Comment 5 Martin Walch 2014-09-05 15:57:04 UTC
Looks to me like the same problem as described in bug #181081.

*** This bug has been marked as a duplicate of bug 181081 ***