Version: (using KDE 4.3.2) This bug has been copied over from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561234 I was playing kbounce, when I encountered a weird problem. I had a section with a ball in it, and was going to shrink it. As the wall had almost fully created, the ball got really close to it, and somehow, both halves filled. The ball wasn't trapped in the wall, and actually bounced out of the playing area. Supposedly. I noticed the walls weren't filling right afterwards. Thanks in advance.
Created attachment 51145 [details] Patch I mostly fixed this bug. I wasn't able to tackle all issues with balls penetrating walls, but most of them are gone. Well, the codebase is not the most advenced one - it would be a good idea to rewrite some parts (e.g. wall finishing mechanism). Note that this bug sometimes causes the balls to escape from board. Because of that, the game accessed vector m_tiles out of bounds. I'm feeling very lucky to not step into SIGSEGV at all :)
Thank you, I move to another flat some weeks ago and in caus of that i dont have a internet access. But now i continue my work on kbounce. I also have some ideas for rewriting some mayor parts of kbounce. But in the meantime i will commit your patch and test it. Cheers Andreas Am Dienstag, 31. August 2010 schrieb Gustaw Smolarczyk: > https://bugs.kde.org/show_bug.cgi?id=228063 > > > > > > --- Comment #1 from Gustaw Smolarczyk <wielkiegie gmail com> 2010-08-31 > 17:13:37 --- Created an attachment (id=51145) > --> (http://bugs.kde.org/attachment.cgi?id=51145) > Patch > > I mostly fixed this bug. I wasn't able to tackle all issues with balls > penetrating walls, but most of them are gone. > > Well, the codebase is not the most advenced one - it would be a good idea > to rewrite some parts (e.g. wall finishing mechanism). > > Note that this bug sometimes causes the balls to escape from board. Because > of that, the game accessed vector m_tiles out of bounds. I'm feeling very > lucky to not step into SIGSEGV at all :)
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.