I request that an itineration counter be added with number of calculated possible itinerations and the number of itinerations completed with the current rebuild operation. I have noticed that sometimes the entire structure will go green when I modify the puzzle and I am assuming that this configuration of the puzzle has not been evaluated and stored in the collective memory of the puzzle possible positiions, but I am not certain on this.

One of the methods that I have found very useful is being able to start at one end of a backbone and select 2 or 3 loops and after completing the process with whatever results I increase the number of loops in the rebuild to 5 or 6 and repeat the process. I don't know of a way of recording the best result other than to use .

I don't know how to automatically stop after all the itinerations have been run or how to determine what quantity of the possible itinerations have been run.

I usually zoom out so far that I cannot see the puzzle at all to conserve on resources and this speeds up the process. This is a little cumbersome but it seems to work for now. Tools to increase the use of the rebuild tool could prove to be very useful since I cannot give the amount of time some of the puzzles require to come to the best result.

If I can code a macro of steps or techniques to run then I would be able to run a bunch of tasks then come back and check the results without having to attend to the display. This may improve my efficiency and enable everyone to codify the sucessful processes, thus enabling these processes to be disseminated broadly. This might contribute to a master process that people can compete against like Big Blue for chess but this would just be an instruction set that is applied in a conditional sequence that yields the highest returns based on the points acquired.

Thanks,
Tim