The score does not display properly past about level 60 or so; all that shows is the 4 least-significant digits. (Like this: Score...7,824) I suspect that the easy fix would be to move the difficulty level selector from the statusbar to the toolbar. My deep appreciation for whomever fixed the 'can't start a line in only one space' problem - it's greatly improved my game play. If possible, adding a 'save game in process' feature would be also appreciated - at the break between rounds would work wonderfully. Another feature I'd love to see would be the 'pause when any other window is activated' feature being made optional - there are times I'd like to do other things while the round is still in process, though I understand that others would enjoy the automatic-pause feature. Reproducible: Always Steps to Reproduce: 1. Play until your score gets too high to display. 2. 3. Actual Results: A score that is over 100,000 displays as Score...7,824 A very minor improvement suggestion would be to display levels completed with the scores in the 'show high scores' popup, as the end of game score ranking shows it.
Hello Dan, thanks for reporting this bug. :-) > The score does not display properly past about level 60 or so; all that > shows is the 4 least-significant digits. (Like this: Score...7,824) I > suspect that the easy fix would be to move the difficulty level selector > from the statusbar to the toolbar. Would you mind to attach a screenshot showing how the bug actually occurs? Right know I have not enough time (neither the ability) to play the game all the way through level 60 or to hack into the code forcing a highscore. A screenshot would be extremely helpful to have a better understanding of the bug. > My deep appreciation for whomever fixed the 'can't start a line in only one > space' problem - it's greatly improved my game play. If possible, adding a > 'save game in process' feature would be also appreciated - at the break > between rounds would work wonderfully. Another feature I'd love to see > would be the 'pause when any other window is activated' feature being made > optional - there are times I'd like to do other things while the round is > still in process, though I understand that others would enjoy the > automatic-pause feature. Thank you very much! I guess this bug got fixed without me even realizing it. I'll consider your thoughts regarding the optional automatic pause feature and, if I find it suitable to implement, find some time for it. Unluckily I can only contribute to KDE on my spare time (something that I've been lacking lately) so you may have to wait a few days (or weeks) until everything gets fixed. > Reproducible: Always > > Steps to Reproduce: > 1. Play until your score gets too high to display. > 2. > 3. > Actual Results: > A score that is over 100,000 displays as Score...7,824 > > > A very minor improvement suggestion would be to display levels completed > with the scores in the 'show high scores' popup, as the end of game score > ranking shows it. That would be a little more difficult since all KDE games use the default highscores dialog provided by libkdegames. Customizing it to integrate better with KBounce would penalize the other games (which I'll certainly won't do) or, if I take the other available approach, add lots of extra code into the current codebase just for a considerably small feature. The drawbacks are just too big. All the best.
Created attachment 86005 [details] bad_score.png Greetings, Roney - thanks for helping on one of my favorite games. :D On 4/7/14, Roney Gomes <roney477@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=332943 > > --- Comment #1 from Roney Gomes <roney477@gmail.com> --- > Hello Dan, thanks for reporting this bug. :-) > >> The score does not display properly past about level 60 or so; all that >> shows is the 4 least-significant digits. (Like this: Score...7,824) I >> suspect that the easy fix would be to move the difficulty level selector >> from the statusbar to the toolbar. > > Would you mind to attach a screenshot showing how the bug actually occurs? > Right know I have not enough time (neither the ability) to play the game > all > the way through level 60 or to hack into the code forcing a highscore. > > A screenshot would be extremely helpful to have a better understanding of > the > bug. The screenshot is attached. It seems to take effect at scores of higher than 99,999 - though I must confess I don't pay that much attention to the score. > >> My deep appreciation for whomever fixed the 'can't start a line in only >> one >> space' problem - it's greatly improved my game play. If possible, adding >> a >> 'save game in process' feature would be also appreciated - at the break >> between rounds would work wonderfully. Another feature I'd love to see >> would be the 'pause when any other window is activated' feature being >> made >> optional - there are times I'd like to do other things while the round is >> still in process, though I understand that others would enjoy the >> automatic-pause feature. > Thank you very much! I guess this bug got fixed without me even realizing > it. > I'll consider your thoughts regarding the optional automatic pause feature > and, > if I find it suitable to implement, find some time for it. > > Unluckily I can only contribute to KDE on my spare time (something that > I've > been lacking lately) so you may have to wait a few days (or weeks) until > everything gets fixed. I fully understand, and appreciate your efforts - it'll happen when it happens, and I'm fine with that. I only spoke up because it'd never happen if it was never reported. A way to turn off the auto-pause feature will be greatly appreciated. With the time spent at the higher levels, being able to do other things on the computer while Kbounce continues working would be a great help. The game I took the screencap from is at a point at which I let it just run for 5 or 10 minutes, which still leaves me 25 minutes to finish the level. There's another stage to the level that wants 5 or more minutes for the balls to bounce into a pattern before I build any more wall, as well. The ability to save a game level to restart with later would also be appreciated quite a bit. I've spent weeks getting a game up to high levels, then had to quit the game to shut down my computer - a way to keep the game going when I powered the computer back up would be lovely. > >> Reproducible: Always >> >> Steps to Reproduce: >> 1. Play until your score gets too high to display. >> 2. >> 3. >> Actual Results: >> A score that is over 100,000 displays as Score...7,824 >> >> >> A very minor improvement suggestion would be to display levels completed >> with the scores in the 'show high scores' popup, as the end of game score >> ranking shows it. > > That would be a little more difficult since all KDE games use the default > highscores dialog provided by libkdegames. Customizing it to integrate > better > with KBounce would penalize the other games (which I'll certainly won't do) > or, > if I take the other available approach, add lots of extra code into the > current > codebase just for a considerably small feature. I agree; if it was an easy fix, it'd be nice, but if it's not easy, it's not worth the effort. > The drawbacks are just too big. > > All the best. > > -- > You are receiving this mail because: > You reported the bug. > Regards, Dan Brady
Hello again Dan, thanks for the screenshot. Regarding your request for a pause feature I have good news. I, with the help of a student, already implemented it during the last Season of KDE. It's working pretty nice and you'll be able to save the game at any time, with a few restrictions of course. :-) I'll have some free time next week during the holidays and thus will be able to perform the final tests and finally merge everything into the master branch. All the best.
multiple issues and suggestions are mentioned in this "bug". they should be split. I'd like to see the save game state suggestion implemented. and we need to hit level 60 to try to reproduce the display bug i have a feeling this might be fixed already