show only browse

[John Esak]

> The intercept is
> really
> > down to only two "if" lines I think and they are fairly 
> simple once you
> see the
> > idea. You will basically be catching all regular keys, and 
> all SPECIAL
> keys
> > ([ENTER], {CRUP], [CDWN], etc.) Then, you can deal with 
> anything the user
> > presses, and even press a few things *for* them.
> 
> Already use @entsel to display the bottom prompts.  

That is the start.  The crucial thing is *intercepting" all the key strokes
@entsel and passing them through to INPUT as you want them passsed... Or
not.  Showing the prompts is nice, but it doesn't gain you any control.

It's this kind of thing I'm talking about. You'd have to find the whole
article... Here is a main part of the idea though...


199  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: gosub legend 'put up the standard filePro prompts
.
200  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: KeyPressed=waitkey
.
201  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If: @sk eq "SAVE"
.
       Then: goto wait
.
202  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If: @sk eq "CRUP" or @sk eq "CDWN" or @sk eq "UTAB" or @sk eq
"DTAB"  .
       Then: pushkey ""{"["{@sk{"]"{"[ENTR]"{"";  goto brw
.
203  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       . If:
.
       Then: '
.
204  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
grp_1  . If: KeyPressed eq "A" or KeyPressed eq "M" or KeyPressed eq "D"
.
       Then:
.



You can deal with the main filePro prompts/@keys and others of your own


John