Request: Auto remove maybes

[GoogleCodeExporter]

It can be troublesome for a user to have to remove maybes when filling in 
definite answers. It would be nice if maybes in the same row and column as a 
definite answer were automatically removed.

The tricky part is deciding how to handle this. A user may accidentally fill in 
a definite answer and clear out maybes that they didn't mean to clear out.

You could use:
* a prompt for every time you fill in a definite answer which will clear maybes
* a checkbox that defaults to unchecked which would clear maybes upon selecting 
a definite answer
* long press a definite answer to clear maybes
* etc

Original issue reported on code.google.com by say...@gmail.com on 30 Dec 2010 at 3:49

[GoogleCodeExporter]

Definitely a useful feature, but as you say, the exact details of the logic 
will be tricky. It is probably worth waiting until there is an undo feature 
(another one to add to the list!), since that will probably help with some 
scenarios (where a user makes a change, but then changes their mind).

Original comment by em...@srlee.com on 31 Dec 2010 at 11:51

• Changed state: Accepted
• Added labels: Component-UI, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Indeed. Just putting this here for the future, but will be nice to consider 
when the time is available.

Original comment by say...@gmail.com on 31 Dec 2010 at 7:29

[GoogleCodeExporter]

I was going to suggest undo in combination with this, and I see someone else 
has.  It might even be nice to have limited auto penciling - like being able to 
auto-pencil anything that is not hard-eliminated, in a single cage.

Original comment by simic...@gmail.com on 28 Mar 2011 at 3:06

[GoogleCodeExporter]

not sure I would find this helpful 

Original comment by andrewdb...@googlemail.com on 8 May 2011 at 5:24

[GoogleCodeExporter]

I've wanted this one for a while. I agree that it feels like it needs 'undo', 
but I find I only want to undo in combination with this feature (and 
multi-level undo feels over the top). The way I've done it here is:

 * Add an option (defaults to off) to automatically remove maybes
 * Adding definite answers clears out any maybes in that row/column
 * Any modified cells are temporarily recoloured to show the user what's changed

I've not added true undo yet, but so far if I make a mistake the colour cues 
are enough to let me go back and repair it. I'll play with it some more and see 
how it feels.

Original comment by MarkHow...@gmail.com on 8 Sep 2011 at 1:51

[GoogleCodeExporter]

@Mark: have you posted your code anywhere? You can add an attachment to your 
comments.

Original comment by say...@gmail.com on 8 Sep 2011 at 5:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Actually, I'd vote against this, as updating the maybe's is a key part of the 
puzzle-solving process. It's easy to miss one and be confounded for a while, or 
suddenly solve a square by noticing you forgot to update a maybe. 

Original comment by dstarf...@gmail.com on 11 Aug 2012 at 7:49

[GoogleCodeExporter]

Resolved in revision85.

Original comment by paul.din...@gmail.com on 15 Mar 2013 at 3:23

• Changed state: Fixed

[GoogleCodeExporter]

https://code.google.com/p/mathdoku/source/detail?r=85

Has this also been set as a user setting? Can users enable/disable this feature?

Original comment by say...@gmail.com on 15 Mar 2013 at 3:34

[GoogleCodeExporter]

Yes this is implemented as a user setting. By default it will be enabled.

Original comment by paul.din...@gmail.com on 17 Mar 2013 at 11:18

• Added labels: Milestone-1.96

[GoogleCodeExporter]

Tested in Revision 163: Maybes are removed automatically if option is set. If 
option is not set, no changes to maybe values are made.

Original comment by em...@srlee.com on 27 Mar 2013 at 12:19

• Changed state: Verified