03-29-2024, 01:33 AM
Add a correctly written _EXIT subroutine and you'd have to use Task manager to close it.
I always coded my own pause routines for my apps. Sleep is nice for pausing when debugging. You can use it with INKEY$ and still get input...
...but that's a pretty Mickey Mouse way to avoid a loop.
You know in 2005 you could do something like this in QuickBasic...
However QB64 doesn't have the lag problem on min, so this little nugget has turned into fool's gold... Oh unless you developers want to break QB64 to make it more 100% QuickBasic compatible!
Pause for a moment and think about it...
Fun stuff.
Pete
I always coded my own pause routines for my apps. Sleep is nice for pausing when debugging. You can use it with INKEY$ and still get input...
Code: (Select All)
Sleep
b$ = InKey$
Print b$
End
...but that's a pretty Mickey Mouse way to avoid a loop.
You know in 2005 you could do something like this in QuickBasic...
Code: (Select All)
Z1 = Timer: Z3 = Timer
Do
'''IF MSE >= 0 THEN EX% = 2: CALL MDRIVER(EX%, B$, POP)
Z2 = Timer
If Z1 > Timer Then Z1 = Z1 - 86400: Rem MIDNIGHT ISSUES
If Z3 > Timer Then Z3 = Z2: Rem MIDNIGHT ISSUES
If Abs(Z2 - Z3) > .2 Then Sound 3000, 3: Z1 = Z2: Rem PROG WAS MINIMIZED
'''IF ABS(Z1 - Z2) > TM THEN CALL SSR
B$ = InKey$
If B$ <> "" Then
'''IF MSE >= 0 THEN EX% = -1: CALL MDRIVER(EX%, B$, POP)
Exit Do
End If
Z3 = Z2
Loop
However QB64 doesn't have the lag problem on min, so this little nugget has turned into fool's gold... Oh unless you developers want to break QB64 to make it more 100% QuickBasic compatible!
Pause for a moment and think about it...
Fun stuff.
Pete