aboutsummaryrefslogtreecommitdiff
path: root/PuzzleApplet.java
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2016-02-24 19:27:10 +0000
committerSimon Tatham <anakin@pobox.com>2016-02-24 19:27:10 +0000
commit32643fab5583c6a0af6fd8373b226198d59d8b99 (patch)
tree329a8d1f20142f9e827f83ebf00973b0e723f5ea /PuzzleApplet.java
parent24848706edfdd1db1f97e3681d7ff52bec2fa575 (diff)
downloadpuzzles-32643fab5583c6a0af6fd8373b226198d59d8b99.zip
puzzles-32643fab5583c6a0af6fd8373b226198d59d8b99.tar.gz
puzzles-32643fab5583c6a0af6fd8373b226198d59d8b99.tar.bz2
puzzles-32643fab5583c6a0af6fd8373b226198d59d8b99.tar.xz
Loopy: be friendlier to right-click-less playing style.
Some people don't bother to use the right-click UI action that marks a line as 'definitely not' rather than the initial default yellow 'unknown'. Previously, Loopy gave those people a UI annoyance for some classes of mistake they made during solving: it would reliably highlight a clue square with too _many_ edges around it, but not one with too few - because in normal right-click-ful play, a clue with too few LINE_YES only becomes an error when there aren't enough LINE_UNKNOWN around it to potentially become the remaining YESes in future. This change arranges that once the player closes the loop, _then_ we light up underfilled clues, on the basis that adding any further edge would be an obvious error, so it's no longer sensible to assume that the user might be planning to come back and do so. (It's not a very timely notification of errors - it's easy to imagine someone making a mistake like this very near the start of play and only finding out about it when they close the loop at the very end. I discuss possible improvements in a comment, but I don't think any improvement avoids that problem completely, so I think it may just be a form of annoyance that right-click-less players have to live with.)
Diffstat (limited to 'PuzzleApplet.java')
0 files changed, 0 insertions, 0 deletions