Bug 339038

Summary: Starting a new game by changing the difficulty leads to an unplayable game
Product: [Applications] kblocks Reporter: Martin Walch <walch.martin>
Component: generalAssignee: Zhongjie Cai <squall.leonhart.cai>
Status: RESOLVED FIXED    
Severity: normal CC: carlw.smart, kde-games-bugs
Priority: NOR    
Version: 0.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: http://commits.kde.org/kblocks/145820a70ce12409873e9326c8c232a790c76081 Version Fixed In:
Sentry Crash Report:

Description Martin Walch 2014-09-12 19:40:59 UTC 
When starting up kblocks and only changing the difficulty via >Settings >Difficulty, without explicitely starting a game, a new game automatically starts (you need to actually change the difficulty, e.g. from "Medium" to "Easy"). However, the keyboard input for that game is ignored.

Note: When using a kblocks version that is still affected by bug #320286, you need to change the difficulty two times to trigger the bug.

Reproducible: Always
Comment 1 Julian Helfferich 2016-02-28 21:00:10 UTC 
Git commit 145820a70ce12409873e9326c8c232a790c76081 by Julian Helfferich.
Committed on 28/02/2016 at 19:46.
Pushed by helfferich into branch 'Applications/15.12'.

Fix unplayable game when changing difficulty

Previously, changing the difficulty before the first game was started
by selecting "Single Game" or "Human vs. AI" started an unplayable
game.

Now, levelChanged() calls singleGame() or pveStepGame() instead of
startGame(). These functions are also called when selecting "Single
Game" or "Human vs. AI", respectively, and correctly connect keyboard
events to the game.
REVIEW: 127171

M  +5    -1    KBlocksWin.cpp

http://commits.kde.org/kblocks/145820a70ce12409873e9326c8c232a790c76081