aboutsummaryrefslogtreecommitdiff
path: root/misc.c
diff options
context:
space:
mode:
authorBen Harris <bjh21@bjh21.me.uk>2022-12-27 16:14:48 +0000
committerBen Harris <bjh21@bjh21.me.uk>2022-12-27 16:34:37 +0000
commit99d3c31e12ac5bb7c12d2b7a59c702cb671e9b62 (patch)
tree13e838987198780efb4e3f83ee4bfd86fba83404 /misc.c
parent4ec2c580453b0629b9935cb1e90017de6d110608 (diff)
downloadpuzzles-99d3c31e12ac5bb7c12d2b7a59c702cb671e9b62.zip
puzzles-99d3c31e12ac5bb7c12d2b7a59c702cb671e9b62.tar.gz
puzzles-99d3c31e12ac5bb7c12d2b7a59c702cb671e9b62.tar.bz2
puzzles-99d3c31e12ac5bb7c12d2b7a59c702cb671e9b62.tar.xz
Tracks: Highlight more counting errors if track looks good
Normally, Tracks puts error marks on row and column clues only when one of the existing track or no-track marks will have to be removed to satisfy the clue. This could lead to a situation where the player had built a track from A to B and got neither a win nor a highlighted error because the only error was in a row or column having too few track segments. This commit re-arranges the completion checking so that if there's a complete track from A to B and no spurious track then the game will highlight any clue that isn't matched by the actually laid track. This should mean that any solution with a track from A to B will either be a win or have a highlighted error. This should fix Android issue #266.
Diffstat (limited to 'misc.c')
0 files changed, 0 insertions, 0 deletions