aboutsummaryrefslogtreecommitdiff
path: root/galaxies.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2023-03-10 18:01:17 +0000
committerSimon Tatham <anakin@pobox.com>2023-03-10 18:46:06 +0000
commit8c5077ee8805e81548b42f093a00f41afdcd4d54 (patch)
tree316845f15897c54a4b6fc1f5630212be13b1e1a3 /galaxies.c
parent4f579ddab55d7c49c3d7413e4da690e6609bfe25 (diff)
downloadpuzzles-8c5077ee8805e81548b42f093a00f41afdcd4d54.zip
puzzles-8c5077ee8805e81548b42f093a00f41afdcd4d54.tar.gz
puzzles-8c5077ee8805e81548b42f093a00f41afdcd4d54.tar.bz2
puzzles-8c5077ee8805e81548b42f093a00f41afdcd4d54.tar.xz
Galaxies: fix edge coordinates in a diagnostic.
The coordinates in this 'Setting edge' message from the solver don't match the coordinates of the edge that is actually set. No wonder the solver output was confusing!
Diffstat (limited to 'galaxies.c')
-rw-r--r--galaxies.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/galaxies.c b/galaxies.c
index 73356fb..246438d 100644
--- a/galaxies.c
+++ b/galaxies.c
@@ -1857,7 +1857,7 @@ static int solver_lines_opposite_cb(game_state *state, space *edge, void *ctx)
if (!(edge_opp->flags & F_EDGE_SET)) {
solvep(("%*sSetting edge %d,%d as opposite %d,%d\n",
solver_recurse_depth*4, "",
- tile_opp->x-dx, tile_opp->y-dy, edge->x, edge->y));
+ tile_opp->x+dx, tile_opp->y+dy, edge->x, edge->y));
edge_opp->flags |= F_EDGE_SET;
didsth = 1;
}