QB.EXE Problem Where SETUEVENT Not Cleared Between Runs (43023)

MORE INFORMATION

The following related problem occurs in both QB.EXE and compiled .EXE programs: after CALL SETUEVENT is invoked just once, each subsequent non-user-defined event (such as ON TIMER, ON COM, ON KEY, or ON PLAY) also improperly activates the user-defined event (ON UEVENT GOSUB) trap. For more information on this related problem, query on the following words:

Steps to Reproduce Problem in QB.EXE

The following program, EVENT1.BAS, sets up a user-defined event trap but never activates it. The second program, EVENT2.BAS, sets up and activates another user-defined event trap.

The first time EVENT1.BAS is run in QB.EXE, the user-defined event trap never occurs (which is correct). If it is run after EVENT2.BAS, the EVENT1 procedure is activated. This is because the SETUEVENT is remembered between the programs.

The steps to reproduce this are as follows:

1. Invoke QB.EXE.
2. Load EVENT1.BAS (it runs correctly).
3. Load EVENT2.BAS and run it.
4. Load EVENT1.BAS again. User event remembers TIMER event.

EVENT1.BAS

CLS
ON UEVENT GOSUB event1
UEVENT ON
DO: LOOP UNTIL INKEY$ <> ""
END

event1:
 PRINT "user event"
 RETURN
				

EVENT2.BAS

'**** PROGRAM #2
CLS
ON UEVENT GOSUB event1
ON TIMER(1) GOSUB timeout
UEVENT ON
TIMER ON
CALL setuevent
DO: LOOP UNTIL INKEY$ <> ""
END
				

timeout:

  PRINT "timeout"
RETURN
				

event1:

  PRINT "user event"
RETURN