Version: unspecified (using KDE 4.6.0) OS: Linux The new KBlocks 0.3 (shipped with KDE 4.6.00) seems to contain a whole set of novel quirks: 1) The game was extremely sluggish to begin with, particularly with the Egyptian theme. After I added the command line parameter '--graphicssystem raster' (never needed before) it became playable. There is still a somewhat longer keyboard latency than in earlier versions. 2) Rotation (clockwise and anti-clockwise) now works in reverse. I.e., in order to make the 'Up' key do an anti-clockwise rotation you must now set it to 'clockwise'. 3) Scoring behaves differently than before: Removing 4 rows at once now gives you 100 points, while in previous versions it was 1200. Nonetheless, my old high score list remains in place - and completely unattainable. 4) If you start a new game right after another, the score from the previous game remains on-screen until the first time points are scored in the new game. 5) Finally,the game seems to stay at its basic speed no matter how long you play it. Previous versions would increase the speed at intervals. (Regarding this point, see also Bug 267859.) Reproducible: Always Steps to Reproduce: Install OpenSuse 11.4 with KDE 4.6 (and with KBlocks 0.3), then play KBlocks. To make the game playable (i.e., not extremely sluggish), you may also need to add the parameter '--graphicssystem raster' - see item 1) in the Details section. Actual Results: I got the quirky behaviour described in the Details section. Expected Results: Relating to the 5 issues described in the details section: 1) Keyboard responsiveness should not deteriorate compared to older versions. 2) The rotation keys ought not to be reversed. 3) Scoring should either work as before, OR the high score list should be cleared. (I am not particularly attached to this list, but it is a bit annoying to have it sitting there with figures that are no longer realistic.) 4) The score from the previous game (in the status line) should be cleared when you start a new one. 5) Game speed should increase at intervals, as has been the case with such games from time immemorial. It is slightly boring to keep running at the same speed indefinitely. This is, of course, a very small matter in the general scheme of things. I am very much impressed by this latest OpenSuse/KDE release. So far this is the only bug I have noticed. Thanks to all concerned for doing such a wonderful job!
Thanks for the report, but could you please split each of these issues out into its own report? Combined reports like this are more difficult for developers to handle, as the issues can't be tracked individually. Just copying and pasting the descriptions from this report should be sufficient.
Following the above request from Parker Coates, I have split this bug report into four new bugs: bug 268583 (for issue 1), bug 268581 (for issue 2), bug 268584 (for issue 3) and bug 268585 (for issue 4). As regards issue 5, that issue seems to have been already reported in bug 267859 - so in this case I added a comment to the existing bug.
Done. I am unsure of what to do with the original bug, though. It can hardly be considered "solved" at this stage, nor does it seem to be in need of further info. I think it should be marked as "closed", but that option does not seem to be available. "Resolved as invalid" might do, I suppose...unless "invalid" is reserved for some other form of misery than the present one. If you feel like it, just change the status of bug 268528 to whatever it should be. News of your decision will reach me by the regular channels, I suppose. On 15-03-2011 14:48, Parker Coates wrote: > https://bugs.kde.org/show_bug.cgi?id=268528 > > > > > > --- Comment #1 from Parker Coates<parker coates kdemail net> 2011-03-15 14:48:04 --- > Thanks for the report, but could you please split each of these issues out into > its own report? Combined reports like this are more difficult for developers to > handle, as the issues can't be tracked individually. Just copying and pasting > the descriptions from this report should be sufficient. >
I still prefer KSirtet because of all those issues :)
Thanks.