Could _EXIT be made to ignore SLEEP and _DELAY?

[Pete]

I don't need this, but someone might.

So this example works okay, but only if it has ON TIMER in it...

Code: QB64: [Select]

1. PRINT "Hold down Esc key until program ends.": PRINT
2.  
3. ON TIMER(1) GOSUB quit
4.  
5. KEY 15, CHR$(1) ' Esc key
6. ON KEY(15) GOSUB break_program
7.  
8. KEY(15) ON
9. TIMER ON
10.  
11. DO
12.     ' Do stuff here...
13.     _DELAY 600 ' Take a break...
14. LOOP
15.  
16. break_program:
17. END
18. RETURN
19.  
20. quit:
21. IF _EXIT THEN CALL exit_warning
22. RETURN
23.  
24. SUB exit_warning
25.     DO
26.         LINE INPUT "Do you want to exit. Y/N ? ", a$
27.         IF UCASE$(a$) = "Y" THEN SYSTEM
28.         IF UCASE$(a$) = "N" OR a$ = "" THEN EXIT DO
29.     LOOP
30. END SUB
31.  

If _EXIT just ignored the SLEEP and _DELAY statements, if that's possible, you would not need the ON TIMER part at all.

Also, there was another thread where the author was trying to decide on using SLEEP vs _DELAY for very long pauses. _DELAY uses a little less resources, but what if he had to break into the program. SLEEP would allow a keypress to break the delay, but _DELAY would require the ON KEY() approach, as posted above, but without the added _EXIT function.

The otehr thing I wanted to mention is the process coded above is clunky. It appears ON TIMER fights a bit with ON KEY(), causing a noticeable delay in executing the key input. That's why I printed the instructions to hold the Esc down, instead of just pressing it. Is there any method to smooth it out?

Pete

[SMcNeill]

Isn't this just a simple case of Write your own function for your specific needs?

Code: QB64: [Select]

1. PRINT "Hold down Esc key until program ends.": PRINT
2.  
3. ON TIMER(1) GOSUB quit
4.  
5. KEY 15, CHR$(1) ' Esc key
6. ON KEY(15) GOSUB break_program
7.  
8. KEY(15) ON
9. TIMER ON
10.  
11. DO
12.     ' Do stuff here...
13.     Delay 600 ' Take a break...
14. LOOP
15.  
16. break_program:
17. END
18. RETURN
19.  
20. quit:
21. IF _EXIT THEN CALL exit_warning
22. RETURN
23.  
24. SUB exit_warning
25.     DO
26.         LINE INPUT "Do you want to exit. Y/N ? ", a$
27.         IF UCASE$(a$) = "Y" THEN SYSTEM
28.         IF UCASE$(a$) = "N" OR a$ = "" THEN EXIT DO
29.     LOOP
30. END SUB
31.  
32. SUB Delay (time AS _FLOAT)
33.     DIM t AS _FLOAT
34.     t = TIMER + time
35.     DO
36.         _DELAY .001
37.     LOOP UNTIL TIMER > t
38. END SUB

Of course, to do this type of thing without midnight overflow, I'd suggest making use of my ExtendedTimer routine, but you can always code around it the OldSkool(tm) way, which you seem to prefer...

[Pete]

Nice, and yes, I have plenty of those timer routines, midnight 86400 adjustment included. So for me, I'd never use _DELAY for anything else that short pauses for display effect.

I'm just thinking the QB64 language could be improved by having the ON TIMER with ON KEY() play better together, without the lag issues with key input, or the _EXIT could be improved by ignoring SLEEP and _DELAY statements, if that's even possible.

So this is not for my personal use, just in regards to the language, for anyone here who still works in that area.

Pete