it has to do with
controlling XyWrite from external programs. It has to do with
the "secret signal" that XyWrite alone, of all the programs on
our computers, is sensitive to, namely key 115 (and also 126).
Now that is pretty amazing.
Indeed. How did you discover it? How come others ignore 115 but Xy doesn't?
Does it have to do with XyWrite using the BIOS directly for its keyboard
stuff?
The implications, and the possibilities,
are huge.
Let's discuss them. I have only a glimmer: we can now write Windows
programs that will do things indirectly in XyWrite (?). And what language
did you write UnDo.exe in? Visual Basic?
It's the real purpose of the $M frame in UnDo's
program suite.
Is that the frame SpclLst?
Although Harry of course elected to use the boring, conventional
Keystroke-generated Method, which doesn't exploit any of this.
Yeah, but remember that I get the credit for even SUGGESTING that an UnDo
program be written. To wit (from 6/17/08):
The only significant feature I know of that other programs have but Xy
lacks is "undo." Yes, the UnDelete function is a little bit of that, but
now we have before us a great opportunity and challenge: write an XPL
routine that gives us at least 3 levels of undo. . . . Maintain "trailing
versions" of the current file, in a separate window (or separate launch of
another iteration of Xy). . . .
Harry Binswanger
hb@xxxxxxxx