Small docs patch from Phil Bordelon adding more history of Sudoku.
Patch from Phil Bordelon to improve Bridges' appearance by adjusting
Tal Kelrich spotted that hitting `Solve' on a configuration which is
Revert a change in an assertion made in r6299. It was right the
Add some random index terms. ("Sudoku" wasn't in the index!)
Laurent Thioudellet reports that gcc4's ultra-cautious data flow
I've just noticed a bug in the Inertia solver: if you call it on an
Correct w/h mixup in grid edge checks.
Document Unix command-line options.
Fix segfault in Tents' printing.
Work around a couple of minor display issues with max bridges set to 4:
Cleanup: relieve frontends of the duty to call
Cleanup: remove the `just_used_solve' field from a number of games
Forgot to update devel.but in r6417.
Cleanup: it was absolutely stupid for game_wants_statusbar() to be a
Cleanup: remove the game_state parameter to game_colours(). No game
Noticed recently that bitcount16() isn't 16-bit clean due to signed
Cleanup: the `mouse_priorities' field in the back end has been a
OS X frontend was directly calling the backend's wants_statusbar()
Cleanup: rename random_init() to random_new(), because it actually
New puzzle from James H: `Bridges', another Nikoli job.
Miscellaneous fixes. Correct a comparison of y with w causing
Just noticed a longhand shuffling operation which I must have missed
Janes H provides a small workaround for a Palm tools bug.
Small error in solver diagnostics.
Revamp of the control mechanism to permit drag- as well as
New puzzle: `Tents'. Requires a potentially shared algorithms module
loopy_diffnames[] isn't used, and provokes a warning on OS X.
Yikes! I've only just noticed that this copy of tree234.c was still
r6384 didn't go quite far enough. In fact, a grid square which
Fixes for handling human-entered Flip games. The clicked-on square
Richard Earnshaw points out that if you enter an out-of-range number
Use game_set_size() to set up the temporary drawstate in
Fix very strange indentation issue!
Bug fix from James H: prevent LINEWIDTH ever reaching zero.
Another optimisation patch from Mike, which (among other things)
Optimisation patch from Mike: remember which squares we've entirely
Patch from Mike: fix an array indexing error in the clue
I am again gormless! When I overhauled Solo's grid generator in
I found a slightly odd-looking line of code in this file a few days
Minor improvement to initial loop generation.
Oops; left some rogue diagnostics in.
Run the final solution-reduction pass in both directions, since
Solve function for Inertia, using what's essentially an approximate
Marginally greater robustness in the face of solve_game() failing to
Completely rewrite the loop-detection algorithm used to check game
Patch from James H which initialises a couple of Windows API object
I arranged that dying after the game was already completed didn't
Take the Windows taskbar into account when deciding on the maximum
Various patches from Ben H: a fix for an outdated comment, a couple
I've dithered a bit in the past about whether or not it's allowable
Patch from Ton van Overbeek to fix a small memory leak in
Patch from Ton van Overbeek to correct Loopy's misplaced line ends
Another global environment-variable override across all games. This
Couple of minor updates to restore accuracy.
Patches from James H. The usual stuff (memory leak fixes and 16-bit
Someone points out that the Solo text formatter would be a lot
Stop Light Up from eating system keypresses, which it was previously
Palm fixes for Loopy from James H: a #ifdef SLOW_SYSTEM, and an
James H's memory leak fixes to Inertia.
James H has implemented a new `Tricky' difficulty level in Light Up:
Ability to drag pencil marks around.
Terribly cunning approach to making the pencil marks look nicer,
Debian requires -lm, where Red Hat didn't.
Ahem; forgot about recursion. Recursive solving now shows its
Now that Map has some seriously complex deductions, it's about time
Forcing chains in Map give rise to a new `Hard' difficulty level.
Implemented a couple more reasoning modes for Extreme difficulty
Backspace and Delete keys now function like Space in Solo.
Ahem. The region density at which things start to get hairy is 2/3
Aesthetic improvements to the Map error indicators:
There seems to be some odd behaviour when GTK is asked to draw an
Fix array bounds violation in the solver. Oops.
OS X seems particularly picky about possibly uninitialised
New puzzle: `Inertia', originally written for Windows by Ben
Trivial doc changes after recent prolificacy.
Memory leak and type safety fixes from James H.
Phil Bordelon points out that the general convention is to orient
Mike points out that I made an error in one of the presets...
Over-enthusiastic assertion introduced in the printing revamp was
Optimiser placation for OS X gcc.
New puzzle: `Loopy', an implementation of Nikoli's `Slither Link' or
Minor update to Solo's documentation due to Extreme mode.
Brand new difficulty level in Solo. The other day Gareth and I
Don't report an error when loading a saved game from the command
James H points out a rogue fprintf in Net's print routine.
Memory leak in the new printing stuff, plus a couple of comment
`Solve' operation on an already solved map without an aux_info was
*blinks* I apparently didn't try _building_ the OS X port since the
Retire redundant print_line_width() in Net: a relic from a failed
Native Windows printing support, using the infrastructure I put in
Richard B points out a cut and paste error.
Bah, there's always one. Remove the now-erroneous `*.py' from the