Earlier quoted context omitted.
Well, at least I'm not the only one who apparently didn't pay attention for half of the tutorial. :)
I didn't have any three-in-a-rows, nor identical rows. What rule are you referring to?
edit: I see you noticed.
31–40 of 165 posts
Earlier quoted context omitted.
Well if you switch the squares on row 3, you have to switch the square on row 1 as well. Otherwise the columns will not have even numbers of red and blue squares.
Oh. It's really confusing to show not only the current mistake but also the mistakes that would be introduced by fixing it.
http://imgur.com/EYF3kzS I don't understand what's wrong here.
Rows 3 and 5 are identical.
The tutorial must use an example where unique rows/columns is the only way to resolve the choice...
Earlier quoted context omitted.
I didn't have any three-in-a-rows, nor identical rows. What rule are you referring to?
Oh ok, rows 3 and 6 are identical. I feel stupid now.
Does this remind any one else of Sudoku? In the same vein at least. Anyways very cool, great job!
I did similarly in a sudoku game, it is an interesting exercise that then colors your thinking about error messages in future programming.
The fact that the game doesn't accept valid solutions besides the one it wants is a turn-off.