Why only VK_F?? keys can be redefined using SetKey()?

[Enrico Maria Giordano]

This is a sample:

Code: Select all  Expand view  RUN

#include "Fivewin.ch"


FUNCTION MAIN()

    LOCAL oDlg

    LOCAL nVar := 0

    SETKEY( ASC( "-" ), { || MsgInfo( "Minus pressed" ) } )
    SETKEY( VK_F2, { || MsgInfo( "F2 pressed" ) } )

    DEFINE DIALOG oDlg

    @ 1, 1 GET nVar OF oDlg;
           PICTURE "99999";
           RIGHT

    @ 3, 1 BUTTON "&Close" OF oDlg ACTION oDlg:End()

    ACTIVATE DIALOG oDlg;
             CENTER

    RETURN NIL

And this is the cause:

Code: Select all  Expand view  RUN

if bKeyAction != nil .and. lAnd( nFlags, 16777216 ) // function Key

Is it intentional?

EMG

[Antonio Linares]

Enrico,

> Is it intentional?

It looks so

Does Clipper allow to use SetKey() with any key ?

[Enrico Maria Giordano]

Does Clipper allow to use SetKey() with any key ?

Yes:

Code: Select all  Expand view  RUN

#include "Inkey.ch"


FUNCTION MAIN()

    LOCAL GetList := {}

    LOCAL nVar := 0

    CLS

    SETKEY( ASC( "-" ), { || QOut( "Minus pressed" ) } )
    SETKEY( K_F2, { || QOut( "F2 pressed" ) } )

    @ 1, 1 GET nVar PICTURE "99999"

    READ

    INKEY( 0 )

    RETURN NIL

EMG

[Antonio Linares]

Enrico,

Then we should remove ".and. lAnd( nFlags, 16777216 )"

Thanks!

[Antonio Linares]

Enrico,

Lets wait a moment... we used that code because function keys provide chars values like standard keys (non function).

If we remove that code, how will we distinct them ?

[Enrico Maria Giordano]

Enrico,

Lets wait a moment... we used that code because function keys provide chars values like standard keys (non function).

If we remove that code, how will we distinct them ?

I don't know, sorry. Let's keep it unchanged till we'll found a solution.

EMG