Auto-reject maybes when number already set

[GoogleCodeExporter]

This is a request:

As the game auto erases maybes when you put down a number, it should not let 
you write down a maybe when you already have that number down in the same row 
or column, not allowing you to set redundant maybes.

Original issue reported on code.google.com by cristoba...@gmail.com on 17 Jul 2013 at 9:30

[GoogleCodeExporter]

Original comment by paul.din...@gmail.com on 21 Jul 2013 at 8:52

• Added labels: Milestone-2.0, Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

To be decided in next release whether it will be implemented. Following needs 
some thinking:
 * If maybe would be blocked if the value is already user, than this should defenitely be true for the normal values as well.
 * It might block game play for others who realize that a normal number is not correct. They have to clear that value before it can be entered as maybe. For example suppose you enter the value a normal value while you intended to enter it as maybe.
 * Highlighting the duplicate maybe value would be more consistent with current game play. This would then only be done in case the option "Mark duplicates" is enabled.

Original comment by paul.din...@gmail.com on 29 Jul 2013 at 7:25

• Added labels: Milestone-Infinity
• Removed labels: Milestone-2.0

[GoogleCodeExporter]

1* I thought that the game already prevented you from entering a duplicate 
normal value if one was already set in the same row/column. I just checked that 
it just highliths it in red background. I wouldn't allow it. I would flash a 
red background warning in the previously set cell for like a second to let the 
player know that the intended operation is being rejected because of a 
collision with a particular cell already set with that value. Maybe what I 
suggested could be a joint functionality "Reject redundants" which doesn't 
allow you to set any normal value or maybe value that causes a conflict with a 
normal value already present in another cell.

2* I'm not sure if I'm following you in this one. I see it as normal to first 
erase a value that you realize is wrong before entering it as a maybe (but 
couldn't that be done by just re-entering it as a maybe in one operation?)

3* What I said in (1*), maybe the best solution would be an option that would 
reject both normal values and maybes so it is consistent. But this would be an 
option, and not rejecting anything (but duplicate maybes highlighted) would be 
another option.

Important aspect about this feature: This feature I describe works perfectly 
(to me it's a must have) with an "all maybes" button, most of all when you are 
playing big and difficult boards. Sometimes you want to fill 4 or 5 cells (or 
more) with all the possible maybes, and with the current version you have to 
click all the maybes one by one and at the same time check that they aren't 
duplicates to normal values already present. With an "all maybes" button and 
the feature I suggest you do that in just one click per cell, as every cell is 
directly filled with all the maybes and only the ones which are possible 
according to the normal values already present in the board. This saves you A 
LOT of time and double checkings. Please think about it.

Thanks for your time reading this and congratulations on this excellent app ;)

Original comment by cristoba...@gmail.com on 29 Jul 2013 at 7:58

[GoogleCodeExporter]

If you implement this, please make it optional. 

Original comment by brad.b.c...@gmail.com on 17 Sep 2013 at 7:54