Trapping @keyB processing
John Esak
john at valar.com
Fri Oct 28 08:21:21 PDT 2005
> > @KEYB processing?
> > We're running on FP 5.0.13.
> >
> > Thanks in advance,
> >
> > --
> > J. Ryan Kelley
> >
> >
>
> Did you see the @entsel code that Howie posted a few
> days ago? That should work for you I think. It uses
> @entsel and waitkey to catch all of the keystrokes. I
> would think that you could modifiy this so that if a
> "B" was pressed you would either do a pushkey "B" to
> get the regular browse, or go to your own code for a
> custom browse - depending on your variable.
>
> You would of course then remove your @keyb processing.
>
> Jeff Harrison
> jeffaharrison at yahoo.com
I think it would help if Jeff had tested his suggestion before suggesting
it. It only took me 3 seconds to write this...
then: end
@keyB if:
then: pushkey "B"; end
to show that this would cause an infinite loop. Do NOT do this.
If you want to accomplish either using the browse or not and still actually
use the B key, you would have to intercept it and do a pushkey of the exact
keystrokes it would take to turn on the browse at the clerk menu, then
continue on pushing the right keys to get to the index you wanted (if that
is the way you wanted to enter the records...) Or, have the browse on
already and do something opposite to this.
Setting a global variable as you mentioned would direct whether they would
get your special B processing instead of the IUA browse.
More information about the Filepro-list
mailing list