PUSHKEY (was Re: @wlf and F5)

[Kenneth Brody]

Quoting Fairlight (Thu, 10 Jan 2008 18:24:31 -0500):
[...]
> 2) You would trigger a recursive loop the second you did a PUSHKEY of the
> same key.  If they coded it intelligently, you shouldn't.  If they didn't,
> you might.  Just depends how PUSHKEY works...does it actually throw it back
> to the input stream file descriptor, or does it just push it through the
> engine further as if it had gotten past that point?
[...]

PUSHKEY works between the two options you list, but it's sort of like your
option 1 -- push the keystrokes into the input stream.  While it doesn't
push them into stdin itself, it does store then to be read by filePro's
high-level input routine.  The next time filePro goes to read a keystroke,
it will see the next item in your PUSHKEYed sequence.  (In other words,
doing something like PUSHKEY "[SAVE]" does not mean "immediately act as if
the SAVE key were pressed", but rather "the next time a keystroke is read,
act as if the SAVE key were pressed".)

Note, of course, that PUSHKEY only affects the current filePro program.
It has no effect on things like PUSHKEY "yes[ENTR]" ; SYSTEM "something",
even if "something" is another filePro program.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com