QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: TerryRitchie on April 27, 2020, 01:33:58 pm
-
Just curious, when did QB64 lose the ability to produce a beep tone by using this?
PRINT CHR$(7) ' ASCII BEL character
While redoing my tutorials I came across this. I'm working on the sound tutorial now and loading some of the old programs didn't beep when they were supposed to.
ASCII values of 7 were used when terminals needed to send an audible alert to users.
-
Just curious, when did QB64 lose the ability to produce a beep tone by using this?
PRINT CHR$(7) ' ASCII BEL character
While redoing my tutorials I came across this. I'm working on the sound tutorial now and loading some of the old programs didn't beep when they were supposed to.
ASCII values of 7 were used when terminals needed to send an audible alert to users.
SDL versions BEEP. GL versions... are all screwed up with the keyboard input behavior!!
-
Hi
Thanks I have never used it for BEEP but it is a good information that let me know also the BEEP statement of QB64
http://qb64.org/wiki/BEEP (http://qb64.org/wiki/BEEP)
QBasic/QuickBASIC
Older programs may attempt to produce a BEEP by printing CHR$(7) to the screen. This is no longer supported in QB64 after version 1.000.
You may have to replace instances of PRINT CHR$(7) in older programs to the BEEP statement to maintain the legacy functionality.
It is always true, I'll never end to learn!
PS I have thought that _CONTROLCHR could affect this, but it is not true
-
As Tempo pointed out it's in the Wiki. I should have looked first before I asked.
@TempodiBasic - Yeah, that's how we old schoolers used to get sound in our text adventure games :-)
Sword fight! beep..beep
Fire breathing dragon! beep..beep..beep
You're dead! beep
-
Pete's posts: Beep, beep, beep, beep