#Popkey developers code

When the procedure is completed, control attempts to return to the line of code following the one last executed. That means when a specified key is pressed, regardless of what process was in effect, control jumps immediately to the specified procedure.

Unfortunately, in order to make the ON KEYs work properly, the detection of these keystrokes is built right into the native event loop, and checking for these keystrokes occurs between each line of code processed. These commands allow developers to trap a number of keystrokes and perform processing based on them. Specify the key or key combination for which to get information. Returns the command associated with the specified ON KEY LABEL. Returns the current setting of the ON KEY command. For example, you can specify LEFTARROW instead of 331. Provides coverage for both the regular alphanumeric keys and similar keys to nKe圜ode, but provides far more readable code. See the Help for the complete listing of funky keys that can be detected, including Alt+Function Keys, Insert, End, and Del. The procedure to run, usually called with a DO command when a key is pressed. Similar to the dreaded GOTO command of the venerable BASIC language (and others), these can lead to code nearly impossible to debug. These commands provide the ability to interrupt the flow of normal event processing by jumping immediately to a routine you’ve created. ON KEY, ON KEY =, ON KEY Label, On(“Key”), POP KEY, PUSH KEY Tells you the inside scoop on every command, function, property, event and method of Visual FoxPro. An irreverent look at how Visual FoxPro really works.

Popkey developers