Created attachment 131639 [details] KPatience Save File After completing the penultimate set of cards, the pile stayed instead of being filed away until the last stack was dealt. After a '9' card was placed on the pile, it was then moved off. This additional card was needed to solve the game, and was stuck with the pile that moved off. It was odd that there were was a spare king on the table.
Created attachment 131640 [details] KPatience Screenshot Screenshot of invalid state with a spare king and a missing '9' card needed to solve the game.
just to confirm, if you load, press undo until the 9 is not on the bottom anymore and click on the pile, it gets put in the wrong place again?
I did not use the Undo function. However, moving the pile to a different slot would "wake" cause it to be moved off.
I am not asking if you did use undo. I'm asking if you do it *now*. load the file, press undo until the 9 is not on the bottom anymore and click on the pile, it gets put in the wrong place again?
Clicking on the pile (just before the '9' is thrown on) has no effect. Taking part of the pile off and then placing it back on causes the whole pile to be moved off.
Can you reproduce the same error using kpat from flathub? https://flathub.org/apps/details/org.kde.kpat
The flathub instance does not provide a dialog box to load the save file. (Neither 'Ctrl+O' nor the 'Game -> Load' option works.)
please run flatpak update You'll get an update of kpat where opening files should work
Done. The error was reproduced using the updated package. Of course, when I go to the step prior and set up the pile correctly, it is moved off before dealing the last deck (which avoids the issue with the '9' card.) This occurs in both versions of the KPatience package.
Can you please record a screencapture and upload somewhere to see what you do? Because with the new kpatience version i can't reproduce the error so probably i'm not understanding what you do.
Created attachment 131711 [details] KPatience Screencapture Requested screencapture attached.
Can you explain what is wrong in that video? It all looks reasonable to me and the 9 doesn't end up in the bottom left anymore, no?
There was an invalid state during normal play where the completed stack was not automatically moved off. In this particular scenario, the stack could be moved around -- or broken up and rearranged -- to trigger the proper transition. It so happened in this particular scenario that there was room to complete that action. If there were no open slots, that could have prevented any further action.
I'm sorry but i really don't understand what you're saying, i'll leave this in reported in case someone else does.
Created attachment 131838 [details] KPatience Screencapture-20200921 Screenshot of another invalid date (captured 20200921.)
Created attachment 131839 [details] KPatience Save File-20200921 Save file of another invalid date (20200921).
Actually during development I had several cases where the application crashed (in debug validations/asserts). Something is fishy with undo/redo
*** Bug 420547 has been marked as a duplicate of this bug. ***
*** Bug 460855 has been marked as a duplicate of this bug. ***
*** Bug 448956 has been marked as a duplicate of this bug. ***
*** Bug 470274 has been marked as a duplicate of this bug. ***
I've experienced a similar situation, also with a 9 of spades being moved down into the completed stacks, in Kubuntu 22.04 LTS while playing Spider. In the message on the bottom left of the screen, the game is unsure whether the game can still be won or not, but my only move is to try to put the stack with an 8 of spades at the top of it onto the stack that has a 10 of spades at the bottom of it, which is an illegal move. It's an interesting bug. SOFTWARE/OS VERSIONS KPatience version: 21.12.3 Operating system: Kubuntu 22.04 KDE Plasma version: 5.24.7 KDE Frameworks version: 5.92.0 Qt version: 5.15.3 Kernel version: 5.15.0-91-generic (64-bit) Graphics Platform: X11
Created attachment 165172 [details] UnwinnableGameSinceTheNineWentDownWithTheAces.png
*** Bug 480189 has been marked as a duplicate of this bug. ***
Created attachment 167890 [details] Entire column disappeared instead of just spades