I don't know about your code, but I'm sure there are linux programs out there to solve this :) I *know* there are linux screen savers like this and some other windows game called tetravex which does the same thing.
On initial glance at your code, it does not look like you have a way of "backing out" bad placements.. like when you hit a dead end in a maze, you have to backtrack a little first and take a different fork when you come to it. But I could be totally clueless as to how your code is supposed to run, not knowing where your macro runs to begin with.
maybe x and o should be next to each other
anonymous
April 12 2005, 02:41:30 UTC
Did you find the solution yet? I havn't much looked at your code yet... but from the image I'd imagine, that x and o shapes might need to be aligned with each other, not xx and oo, but xo and ox erich AT SIMS berkeley
Re: maybe x and o should be next to each otherdag29580863April 12 2005, 03:21:02 UTC
Gee, it's been a while since that post! I just looked at my version of the program again, and it turns out that I had actually tried that, at one point. It makes the problem a lot easier though. You get a large number of solutions, and they claim there should be a unique solution.
If you do try to run the code, you'll see there needs to be a ++ increment operator in the loop() macro. LJ seems to eat plusses in posts, when you preview them.
Comments 4
On initial glance at your code, it does not look like you have a way of "backing out" bad placements.. like when you hit a dead end in a maze, you have to backtrack a little first and take a different fork when you come to it. But I could be totally clueless as to how your code is supposed to run, not knowing where your macro runs to begin with.
Reply
I havn't much looked at your code yet... but from the image I'd imagine, that x and o shapes might need to be aligned with each other, not xx and oo, but xo and ox
erich AT SIMS berkeley
Reply
If you do try to run the code, you'll see there needs to be a ++ increment operator in the loop() macro. LJ seems to eat plusses in posts, when you preview them.
Reply
Reply
Leave a comment