12-01-2020, 02:50 AM
(This post was last modified: 12-01-2020, 02:51 AM by dale walton.)
Thanks for the insights. However your guess proves incorrect:
To isolate the problem further, I removed the complicated code in "Dist2Nearest" and replaced it with the integer 4. -- see attached.
This code now means (among other things that I am not asking you to analyse or understand) that after the first piece is placed, no position at a distance of 4 along a line of site should be playable. However, when the piece is placed in the corner there is a position at a distance of 4 that IS playable. Why is that so?
I think it has something to do with this position being the only position available at a distance of 4.
To isolate the problem further, I removed the complicated code in "Dist2Nearest" and replaced it with the integer 4. -- see attached.
This code now means (among other things that I am not asking you to analyse or understand) that after the first piece is placed, no position at a distance of 4 along a line of site should be playable. However, when the piece is placed in the corner there is a position at a distance of 4 that IS playable. Why is that so?
I think it has something to do with this position being the only position available at a distance of 4.