Author: Richard A. Fowell (fowell@netcom.com)
Date: 23:34:23 06/02/98
Go up one level in this thread
<snip> >A few years ago I built a good autotester that did not >require any support from the programmers. It was for DOS >and I basically had a memory resident routine that tested >the graphical output for state changes 3 or 4 times per >second. When it found and decoded a move, it would pass >the info to the other computer via the serial port. The >move would be applied by using a keyboard stuff routine >to simulate physical keypresses. It was very reliable >(after lot's of debugging) and used almost no additional >resources. You only needed 2 computers. The overhead >was a tiny fraction of a percent, it was almost immesurable >and both programs had the same overhead although one was >designated the master. > >When I got a new program, I would write a simple configuration >file and this would make the new program testable. It >was very cool. The configuration file would identify key >pixels, and keystrokes required to operate various features. > >I think it would be desirable to have this for windows, and >with the option for a program to donate this information to >the interface. I don't know if programming this for windows >would be as easy since you are probably more isolated from >low level stuff. > >Just a few thoughts. > >- Don Cute idea. I suspect that the move detection, at least, could be done. The Gif-gIf-giF utility at http://www.peda.com does screen monitoring for Win3.1/Win95/Macintosh. I'm not sure about the move input part.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.