Closed GoogleCodeExporter closed 9 years ago
I agree that this would be an interesting option to offer.
Because of the way the application is written, it shouldn't be particularly
difficult to implement. My only concern is how difficult (i.e. time consuming)
it will be for the android device to create a puzzle with a unique solution.
P.S. Like the video!
Original comment by em...@srlee.com
on 18 Dec 2010 at 7:38
I'm not sure its harder at all to ensure a unique solution. Just create a
unique regular puzzle, and then simply hide the operation signs when drawing
the cells.
Original comment by bbux...@gmail.com
on 28 Dec 2010 at 11:40
The problem is that by hiding the operations signs, you have more possibilities
and a unique regular puzzle may become non-unique.
For example, SolutionsOperators.png shows a puzzle with operators with a unique
solution. By hiding the operators, the 3 cage in the bottom right now has more
maybes (it was 1,2 for "3+"; now it could also be 1,3 for "3/" or 1,4 for
"3-"). Because of this, there is now another possible solution (see
SolutionNoOperators.png and imagine the operators were hidden).
Original comment by em...@srlee.com
on 28 Dec 2010 at 2:54
Attachments:
Added option to hide operation signs. Puzzle generation takes a little longer
(since it has more possibilities to check for a unique solution), but still
acceptable (IMHO).
There is a new checkbox on the options screen to control this. Not sure this is
the best place for it - possibly better would be a checkbox at the top of the
New Game sub-menu (where you choose the size of the grid), but I haven't worked
out how to do this yet!
Revision 65
Mathdoku v1.8 Beta 3 available from download page
Original comment by em...@srlee.com
on 15 Jan 2011 at 12:22
Changed the way the option works - Hide Operators is now tri-state: "Always",
"Never", "Ask". If user selects "Ask", then an additional dialog appears when
starting a New Game.
Revision 67
Mathdoku v1.8 Beta 4 available from download page
Original comment by em...@srlee.com
on 17 Jan 2011 at 7:33
V1.8 released to Market
Original comment by em...@srlee.com
on 23 Jan 2011 at 1:49
Original comment by paul.din...@gmail.com
on 15 Mar 2013 at 2:45
Original issue reported on code.google.com by
say...@gmail.com
on 8 Dec 2010 at 9:17