Re: T,r,i,c,k, ,o,r, ,t,r,e,a,t,!

["Carl L. Distefano" CLDistefano@xxxxxxxx]

** Reply to note from Harry Binswanger  Fri, 1 Nov 96 11:45:49 +0000
 
> Does anyone use the native Xy4 macro "capturing keystrokes" facility? I've
> been sort of afraid of it.

Harry: Your fear is understandable, since the native facility affords
little control over the process of recording keystrokes.

Basically, the way it works is this: Func RK toggles keystroke-
recording on and off. So, you hit func RK, perform the keystrokes you
want to record, then hit func RK again. (VAriable $RK returns the
recording state: 1=ON, 0=OFF.) You play back the last set of recorded
keystrokes by hitting func RX. It's not a programming aid in any
meaningful sense. For one, there's a feedback problem in that you
always capture at least one unwanted keystroke, viz, the one that turns
recording off. Furthermore, I don't think there's a way to write down
the XPL code corresponding to the recorded keystrokes. If Scroll Lock
is on, func RX dumps XPL code into the current window. However, I
don't recommend using Scroll Lock, because there's no way of turning
it off once it's on, due to the feedback loop. Maybe Tim B. knows a
better way.

KBDMACRO, of course, isn't a macro recorder. Rather, it transfers
keyboard-file capabilities to the command line, making it easier to
"roll your own". Who devotes a key to, say, DeFining 5 lines? With
KBDMACRO, it's done easily with KB dldldldldl. In short, you
have a single key, , that performs any keyboard-definable
function, on demand.

--------------
Carl Distefano * * * CLDistefano@xxxxxxxx
--------------