simon-git: puzzles (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  3264d56 Fix display glitch in Jigsaw Solo's pencil-mode cursor.
  3ae90bc Map: document explicitly that initial regions are immutable.
  96d65e8 Untangle: turn #define SHOW_CROSSINGS into a preference.

Repository:     https://git.tartarus.org/simon/puzzles.git
On the web:     https://git.tartarus.org/?p=simon/puzzles.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2023-11-14 13:03:12

commit 3264d56791081138348524ce067f87307833d4b0
web diff https://git.tartarus.org/?p=simon/puzzles.git;a=commitdiff;h=3264d56791081138348524ce067f87307833d4b0;hp=35f796542ee5d7e775643f526973aa75f483bf20
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue Nov 14 12:36:41 2023 +0000

    Fix display glitch in Jigsaw Solo's pencil-mode cursor.
    
    In Jigsaw Solo, block boundaries aren't convex, so it's possible for
    one of them to have an inward corner. If that corner is in the top
    left of a selectable cell, and you right-click that cell to display
    the pencil-mode 'cursor' in the form of a triangle in the top left,
    then the cursor was accidentally drawn on top of the block boundary,
    where it ought to be underneath it.
    
    For example, in game id 5j:d1d4_4c3_1d2d,bb_baaa_dca_baaba, right-
    clicking in the bottom right square of the grid demonstrates the
    problem.
    
    Jonas Kölker fixed this for Keen in 2015, in commit 6482ed0e3c886af.
    This is the identical fix, in Solo's very similar-looking drawing
    routine. I feel embarrassed to have taken eight years to get round to
    it!

 solo.c | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

commit 3ae90bcd3a345a932c6bc62cbb985a610caa78f2
web diff https://git.tartarus.org/?p=simon/puzzles.git;a=commitdiff;h=3ae90bcd3a345a932c6bc62cbb985a610caa78f2;hp=3264d56791081138348524ce067f87307833d4b0
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue Nov 14 12:41:46 2023 +0000

    Map: document explicitly that initial regions are immutable.
    
    Chris Boyle reports that a few users of the Android port were confused
    by this, e.g. https://github.com/chrisboyle/sgtpuzzles/issues/624 .
    
    (That seems surprising to me, since I view Map as extremely closely
    related to Solo - both are special cases of the general game class
    'here is a partial k-colouring of a graph, find the unique total
    k-colouring that extends it', just with different ranges of k and
    different valid graphs. And surely nobody approaches a Sudoku puzzle
    and expects to be able to rub out provided clues they don't like! But
    I suppose if you're thinking of Map as a completely separate puzzle
    then perhaps that analogy doesn't have the same force.)

 puzzles.but | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 96d65e852cea8a95001fa70e3ec2996d4ea5e2b4
web diff https://git.tartarus.org/?p=simon/puzzles.git;a=commitdiff;h=96d65e852cea8a95001fa70e3ec2996d4ea5e2b4;hp=3ae90bcd3a345a932c6bc62cbb985a610caa78f2
Author: Simon Tatham <anakin at pobox.com>
Date:   Tue Nov 14 12:59:44 2023 +0000

    Untangle: turn #define SHOW_CROSSINGS into a preference.
    
    I just found this #define in the Untangle source code, which I'd
    completely forgotten was there. It causes each graph edge to be
    highlighted in red if another edge crosses it, so that when you only
    have a small number of crossings left to sort out, it's obvious where
    they are.
    
    Now we have a preferences system, there's no need to make this a
    compile-time option! We can make it run-time selectable, for users who
    want the extra help.

 untangle.c | 46 +++++++++++++++++++---------------------------
 1 file changed, 19 insertions(+), 27 deletions(-)