pushkey
Brian K. White
brian at aljex.com
Thu Jun 24 11:55:03 PDT 2010
On 6/24/2010 2:00 PM, ROBERT PULLIAM wrote:
> Using SCO unix and filepro 5.0.08D
>
> PROCESSING IS AS FOLLOWS
>
> IF qd = "N" or qd = "N"
> THEN pushkey "[brky] [brky] [brky] [brky] X"
>
> AND IN ANOTHER INSTANCE
>
>
> IF QD = "R" OR QD = "r"
> THEN pushkey "[brky] [brky]";end
>
>
> these worked for years but suddenly no longer work after some other processing added. I have used debugger and the processing gets to the proper place and qd is equal to n or r but these lines are
> ignored.
>
>
> Thanks in advance Robert Pulliam
>
I would use "eq" instead of "=" in all If: lines, but that shouldn't be
your problem.
I would capitalize the key codes since that's what's in the manual, but
if it used to work that way then that too shouldn't be your problem.
I would not put any spaces between the key codes unless you really
wanted to simulate the user hitting space bar, just on general
principle, but again if it used to work that way then that too shouldn't
be your problem.
I thought you couldn't use or test for pushkey in the debugger since the
debugger itself "eats" the pushed keys?
How do you know the lines are ignored? Did you add a show or msgbox
statement to them before and/or after the existing contents? Did the
debugger say they test false at the same time the debugger says the
value of qd is "r" ? Did the debugger say it's true but the msgbox/show
never appeared? Did the debugger show that processing ever even reached
these lines?
finally, and this must be it as far as I can tell from this little info,
maybe you have simply disabled BREAK somehow? Did you add a BREAK OFF
command somewhere? Did you disable or change the BREAK key in the shell
before entering fp? Did you change your termcap file or TERM variable
which might cause fp to misinterpret or not recognize what key BREAK
currently is? Several different things could affect BREAK functionality
from processing to environment variables to fp and system termcap files
to the stty command which might appear in scripts like /etc/profile to
built-in defaults for different shells and different tty-providing
daemons (telnet vs ssh vs facetwin vs serial vs console vs X...)
--
bkw
More information about the Filepro-list
mailing list