Version: (using KDE 4.2.3) Installed from: Fedora RPMs Sometimes the game states that there are no more moves and ends the game even if I see there are some moves. This seems like a race condition. It usually happens if one move produces an "avalanche of moves" - the game ends even before all the moves are finished. Is checking for more moves done in a separate thread?
Threading certainly is not the problem: The game has a job queue internally, where a calculation job is scheduled when no moves can be made any more. It might be that an error is inside this queueing. I doubt I will be able to investigate this before the 4.3 release.
Sorry for not coming back to this problem again. If you run into this problem again, could you please post a screenshot? It might be that the code that searches for possible moves is missing some possible constellations.
Created attachment 38974 [details] Screenshot of finished game with moves left
Created attachment 47577 [details] Incorrect hints (1st screenshot) I have just encountered a situation where there are no more moves (I cannot see them at least) and the game says there are 3 moves left. The 3 hints concerning the possible moves are incorrect. I guess this bug might have the same origin as my original report.
Created attachment 47578 [details] Incorrect hints (2nd screenshot)
Created attachment 47579 [details] Incorrect hints (3rd screenshot)
*** Bug 242198 has been marked as a duplicate of this bug. ***
I have checked the code again, but I cannot see any error in the move counting code.
Created attachment 80649 [details] snapshot of the problem
Created attachment 80650 [details] snapshot of the problem sorry for previous bad insertion of an attachment
Could be caused by the animations, i.e. during the animation, no moves are possible, but once it settled, there are. A similar bug can sometimes be seen in ksame.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!