Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Suppressing User Input
Message
De
26/11/2008 10:17:07
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
26/11/2008 07:21:34
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:
01364194
Vues:
16
>>>Why does the PUSH KEY CLEAR and POP KEY not work? I thought that's what they were for? To clear the last ON KEY LABEL commands in the stack and then pull them back.
>>
>>I don't know why they don't work. I don't use OKL unless I purposefully need an intercommand interrupt so I don't run into using PUSH KEY and POP KEY at all. For key shortcuts I usually use a menu defined but not displayed and assign the keys to the menu bars. Then I can use set skip to turn the individual keys on or off as needed and the menu is only available when VFP is in a user input mode automatically so there is no need to turn the keys on and off as code blocks execute, the menu isn't available while code is running.
>
>Well, even using ON KEY or ON KEY LABEL F7 or ON KEY LABEL F7 * or ON KEY LABEL F7 STORE .F. TO VarForNothing, the F7 hotkey still interrupts the processing. We must have something else going on. Is there a way to find out where in the processing that the key is being allowed to activate? The processing is all reasonably new code that does not contain @SAY stuff, so there are no hidden READ/DO EVENTS or anything like that that I'm aware of.

A popup with F7 as the key?

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform