Trapping @keyB processing

[John Esak]

Yes, the @entsel thing is totaly possible. It will save you LOTS of trouble
if you take the time to find the article I wrote on this procedure which is
in an fPDJ somewhere on www.hvcomputer.com .  Believe me... please... there
are SO many gotcha's with this technique... you will be coding for days
otherwise... and STILL you will probably find some I haven't found yet.
Many/most are covered in the article, but since then I have found several
others.

I know Jeff was suggesting a good idea. My suggestion is go for it... but do
not take this project lightly... it is a bear to get right, and I guarantee
you will be tweaking whatever you write for weeks and months. The article
will help shorten this time a lot... but you will still run into strange
things you need to do viz running @keyf forms and other things.

Good luck,

John

By the way what do people call you, Ryan? J?  :-)  Didn't know what to put
at the top of this note.


> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of J. Ryan
> Kelley
> Sent: Friday, October 28, 2005 11:39 AM
> To: Fplist (E-mail)
> Subject: Re: Trapping @keyB processing
>
>
>
>
> John Esak wrote:
>
> >>>@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.
> >
> >
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
> >
> >
> John, I that you misunderstood Jeffs idea, he wasn't suggesting to do a
> pushkey "B" in @keyB.  He is suggesting to trap the B key in @entsel
> processing, of course putting @keyB pushkey "B" would cause an eternal
> loop, but using a waitkey in @entsel just might work....the only problem
> I can forsee is that I'll have to catch every single key for which we
> have processing (which is a lot), but if I put the waitkey into a
> variable, zz, then if zz is not equal to 'B' I could pushkey zz....I
> plan to test this out and I'll let you know what I find, the theory
> seems sound though.
>
> Thanks,
>
> --
> J. Ryan Kelley
> Trinity Transport, Inc.
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list