Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Suppressing User Input
Message
De
24/11/2008 22:37:08
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01363890
Message ID:
01363904
Vues:
18
>>>>>>In the other message, you said lock the keyboard, but this is locking all windows. Is that the same thing?
>>>>>>
>>>>>It prevents any intervention for the application (the user can do nothing with the application, but can work in Office and do other stuff).
>>>>
>>>>I don't understand the usage. What is the parameter when it is not 0?
>>>
>>>If you pass .T. it locks the window, if you pass .F. it unlocks it.
>>>
>>>tlLock implies that the parameter is logical type (True or false)
>>
>>I thought handles were numeric.
>
>Yes, handles are numeric. But the method ReallyLockScreen is used with logical parameter. If you just want to use this Windows API pass 0 to unlock and windows handle (thisform.hwnd) or _screen.hwnd to the function.

Ok, doesn't work for me. We have an @SAY PRG calling the function in another PRG. No matter how I wrap it with the code you gave me, I can still hit F7 hotkey and have it function immediately after the code to lock _SCREEN has been run. It seems to have no affect.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform