The code is intended to work as follows: when only the Enter key is pressed, the variable (H#) cannot be set to zero. However, when the zero (0) key is pressed, the variable (H#) is supposed to have a zero value. But if the entered number is 1,2,3,4,5,6 digits, it is to be confirmed with the Enter key. However, the 7-digit number is to be approved automatically.
To sum up, the entered numbers may have the following values: 0, 11, 232, 1254, 36547, 325478, 3254657.

H$ = "": B$ = ""
WHILE LEN(H$) < 7 AND B$ <> CHR$(13)
    B$ = ""
    WHILE B$ = "": B$ = INKEY$: _LIMIT 30: WEND
    IF B$ = CHR$(27) THEN 4200
    IF B$ = CHR$(32) THEN 8425
    IF B$ = CHR$(45) THEN 6171
    IF B$ = CHR$(43) THEN 6172
    IF B$ = CHR$(81) OR B$ = CHR$(113) THEN 6304
    IF B$ = CHR$(65) OR B$ = CHR$(97) THEN 6305
    IF B$ = CHR$(87) OR B$ = CHR$(119) THEN 6306
    IF B$ = CHR$(83) OR B$ = CHR$(115) THEN 6307
    IF B$ = CHR$(69) OR B$ = CHR$(101) THEN 6308
    IF B$ = CHR$(68) OR B$ = CHR$(100) THEN 6309
    IF B$ = CHR$(82) OR B$ = CHR$(114) THEN 6310
    IF B$ = CHR$(70) OR B$ = CHR$(102) THEN 6311
    IF B$ <> CHR$(13) THEN H$ = H$ + B$
WEND
H# = VAL(H$): PRINT H#

Thank you for your help - regards

I'm working on some very simple games for users of the tutorial to tear apart and learn from.

The very first computer game I ever played was a text race car game on the TRS-80 Model I in 1980.

I've recreated it here for your ASCII enjoyment.

So here's an interesting notice I received from Defender. Hope to hell this kind of threat isn't common or ongoing.

   

Two of the simplest little routines in the world, though I think they'll both end up becoming something I rely on more often in the future:

Sub SaveScreen (Image As Long, SaveTo As _MEM)

    Dim m As _MEM

    m = _MemImage(Image)

    SaveTo = _MemNew(m.SIZE)

    _MemCopy m, m.OFFSET, m.SIZE To SaveTo, SaveTo.OFFSET

    _MemFree m

End Sub



Sub RestoreScreen (FromWhich As _MEM, Image As Long)

    Dim m As _MEM

    m = _MemImage(Image)

    _MemCopy FromWhich, FromWhich.OFFSET, FromWhich.SIZE To m, m.OFFSET

    _MemFree m

End Sub

Screen _NewImage(640, 480, 32)

$Color:32

Cls , Pink

Print "An original Pink screen"

Sleep

GreenFoo

Sleep



Screen 0

Cls , 4 'redscreen

Print "A Red TEXT Screen 0"

Sleep

WhiteFoo







Sub GreenFoo

    Dim Saver As _MEM

    SaveScreen _Display, Saver

    Cls , Green

    Print "A happy Green screen"

    Sleep

    RestoreScreen Saver, _Display

    _MemFree Saver

End Sub



Sub WhiteFoo

    Dim Saver As _MEM

    SaveScreen _Display, Saver

    Cls , 15

    Print "Replaced with white"

    Sleep

    RestoreScreen Saver, _Display

    _MemFree Saver

End Sub







Sub SaveScreen (Image As Long, SaveTo As _MEM)

    Dim m As _MEM

    m = _MemImage(Image)

    SaveTo = _MemNew(m.SIZE)

    _MemCopy m, m.OFFSET, m.SIZE To SaveTo, SaveTo.OFFSET

    _MemFree m

End Sub



Sub RestoreScreen (FromWhich As _MEM, Image As Long)

    Dim m As _MEM

    m = _MemImage(Image)

    _MemCopy FromWhich, FromWhich.OFFSET, FromWhich.SIZE To m, m.OFFSET

    _MemFree m

End Sub

I am no good at graphics. It is not my forte. However, I am somewhat decent at filming and photography. So, my idea is to use my new system for converting images into ASCII text files and making a game using real actors for the main characters, some sort of pixel art characters for the enemies, and AI art for the bosses. All will be converted into ASCII text files that will contain all animation data for their movesets. Basically the entire screen will be created using PRINTSTRING and other PRINT commands. Collision will be fairly easy, as I will have tags on the boundary of each character that will not be printed but will be checked for proximity to another character's tag. If the tags are touching, there is collision. I'm even considering going as far as having cutscenes in the game, with varying degrees of detail provided by the ASCII conversion, so as to have cinematic qualities. Note, this will be my first game EVER, so expect development to be long and arduous, with me asking many of our resident game programmers for assistance. I don't know when I will start this project, but I also don't want people hounding me about it as I'm very bad about getting sidetracked and starting multiple projects at the same time and never finishing them. For the game, I'm thinking typical sidescroller with basic combat. Melee, ranged, etc. I am on call this week for work so I probably won't do much this week but Monday & Tuesday of next week will be a good time for me to start. I want to at least get a first character put on the screen with basic animations for idling, walking, running, and jumping. The hopes for this game will be that it will be compatible with not only QB64 (on all platforms) but that it will also run on QBJS. Shouldn't be too difficult to make that happen. The game probably won't be open source at first, but snippets might be shared for helping with debugging and whatnot.

Am I wrong again? (I often am)!
In the Wiki (and the Help file) I think there may be an error in the explanation for a pause in the Play function.
It says that Pn will pause for n quarter-notes, when it actually pauses for  1/n th. So p1 pauses longer than say, p16.
It's quite easy to adjust the string, but it's confusing.

As it seems everyone is always trying to make their stuff run as fast as possible, I want to take a moment to once again point out the difference in speed between using STRING manipulation (such as MID$) verses the equivalent numeric manipulation (such as with ASC).

Take a brief moment to look at the following code, and compare the run times of these two simple routines:

DEFLNG A-Z

CONST Limit = 100000000 '100 million



DIM s AS STRING

s = STRING$(Limit, "A") 'a string Limit characters long of all "A".



t# = TIMER

FOR i = 1 TO Limit

    IF MID$(s, i, 1) = "A" THEN MID$(s, i, 1) = "B"

NEXT

t1# = TIMER

FOR i = 1 TO Limit

    IF ASC(s, i) = 66 THEN ASC(s, i) = 67 'replace "B" with "C"

NEXT

t2# = TIMER



PRINT USING "###.### seconds to replace with MID$."; t1# - t#

PRINT USING "###.### seconds to replace with ASC."; t2# - t1#



PRINT LEFT$(s, 10) 'just to show we're all "C" now, so we know both replacements worked.

This is a simplified part of a more complex process to split 1 huge inFile into multiple smaller outFile() ones:

Inspired by the thread started by mnrvovrfc (https://qb64phoenix.com/forum/showthread.php?tid=2112), I converted the whole Rick Astley - Never Gonna Give You Up music video to an ASCII animation.

And the code:

Option Explicit

$NoPrefix



Screen NewImage(80, 25)



'You know the rules and so do I

Sleep

Open "B", 1, "rickroll.txt"

Dim As Long x

Dim As String pic, buf

Dim As Long s: s = SndOpen("02 - Rick Astley - Never Gonna Give You Up.flac", "STREAM")

If s Then SndPlay (s)

While Not EOF(1)

    For x = 0 To 24

        If EOF(1) = 0 Then

            Line Input #1, buf

            pic = pic + buf

        End If

    Next

    Cls

    Print Mid$(pic, 2)

    Limit 60

    pic = ""

    If EOF(1) Then Exit While

Wend

Close

I just saw where Spriggsy posted this great new algorithm.

Click this link to try it out in QBJS.

Attached Files

  rr.zip (Size: 93.86 KB / Downloads: 144)