XQUIT PROCESSING (753)    HELP FRAME (9.2)

Name Value
NAME XQUIT PROCESSING
HEADER Changes in XQUIT Processing
TEXT
 
 
   2.  The Menu System just stopped and the programmer had no [control]
       over what happened next, while the Menu System itself had no
       idea what the problem was.
  
   3.  The users recieved a [message] about an XQUIT being encountered 
       that made little or no sense to them.
 
We have corrected these 3 problems.  Notice we do not say "3 features."
     During the execution of an [Entry Action] of an option the
application programmer has always had the option of setting the XQUIT
variable.  When the menu system found this variable it would stop.  There
were 3 major problems inherent in this approach:
  
   1.  The user was [left] at the option where the XQUIT was detected,
       which could well be in the middle of a jump, which caused
       major confusion.
RELATED FRAME
DATE ENTERED 1998-04-15 13:04:00
AUTHOR USER,ONE