GNOME Bugzilla – Bug 731640
Restore Sudoku Tracker
Last modified: 2018-05-22 12:24:37 UTC
Mario's suggestion: - You'd snapshot game states you like or wanna backtrack from with one press and can return to any of your snapshots to (return to that specific game state). I'd like to add - - On clicking 'Clear Board', snapshot of the board state should automatically get added to the tracker The mockups don't have tracker design included, so that also has to be worked on.
Maybe if we add a camera Symbol somewhere. First press creates snapsot. Nest press is a popover with the list oft snapshots and New snapshot. Maybe.
One detail we may (or may not) want to retain: after creating a new snapshot, all further moves appear in a different color (which should be somehow associated with that snapshot) so that it's easy to see what is a guess and what is not.
I've started to work on the tracker backend, and I've 2 questions - - When a user restores a previous snapshot, what should happen to the Undo/Redo stacks ? Retaining them does not make much sense because the strategies get diverged. - Suppose a user filled almost all of the squares and found out he was on the wrong track. So he restores his game to a very early snapshot having only a few squares filled. He then goes on filling correct values and takes a snapshot. Where should this snapshot go ? At the end ? or just after the one he restored ? If we think of individual strategies as branches, it should go just after the one he restored. But since it's the latest, it should go at the end. I'm confused :-( Maybe this will also confuse the user.
please add this to the 1st question: suppose the user restores a snapshot just to see where he went wrong and if we haven't retained the stacks, he won't be able to go back even a single move. We really need to strike a balance b/w Undo/Redo and Previous/Next snapshots. Both provide almost same functionality (if you think of undo is rewind, previous snapshot is nothing but XXL rewind) and thats why I'm afraid that they can clash.
Yeah, you have to preserve undo/redo. Two ways to do this: a) store undo/redo stacks separately for each snapshot b) require that each snapshot be a point on the same undo/redo stack I'd favor (b) because it is simpler: it prevents branching, solving your second question as well.
(In reply to comment #3) > - Suppose a user filled almost all of the squares and found out he was on the > wrong track. So he restores his game to a very early snapshot having only a few > squares filled. He then goes on filling correct values and takes a snapshot. > Where should this snapshot go ? > At the end ? or just after the one he restored ? Let's say the original snapshot is Snapshot A, the user plays on until Snapshot B, then goes back to Snapshot A, branches and plays to Snapshot C. The question is where Snapshot C should be presented, corrected? > If we think of individual strategies as branches, it should go just after the > one he restored. I don't think so. Snapshot C is not somehow superior to Snapshot B, or more closely related to Snapshot A than Snapshot B is. They're on different, unrelated branches. > But since it's the latest, it should go at the end. I'm confused :-( > Maybe this will also confuse the user. I'd say at the end. If we allow branching and try to depict it with a linear UI, then it's necessarily going to be somewhat confusing. :/
Created attachment 280552 [details] [review] Sudoku Tracker Demo This patch has the Tracker backend and a simple design to restore snapshots. The camera button next to Redo adds a snapshot, and the rewind button to the left of Undo restores previous snapshot. On restoring a snapshot, your board and Undo,Redo stacks will be replaced with the ones at the time of capture.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-sudoku/issues/6.