IdleLoop
I'm going to do something different this time around. Usually I would make a new program, illustrating a new concept. However, this time, I won't be doing something new and exciting. I'll be doing something that is old and boring: idle loop.
What is idle loop? Well, you know the main loop on the program that goes like this:
- @MAINLOOP
- 'get player input
- 'process player input
- GOTO @MAINLOOP
That's it. Idle loop is so called because if the player has no input, it'll just wait around doing nothing. In other words, being idle.
So, you're probably wondering why I want to show that here. Shouldn't that process be known to everybody? Yes, it should. But not to everybody. Just like loop, there are various situations that you have to watch out for. For example, where would you want to put the @INIT function?
INIT function deals with initial state of the program. This is where default values come into play. Also, I like to put in @QUIT function, where the program does clean up when it exits. I don't put it in all my programs, especially simple ones, but for completeness, I want my programs to clean up after itself. It's just good programming practice.
So, the structure would be
- Global settings, DIM, and such
- INIT function
- MAIN function
- END/QUIT/CLEANUP function
There is a difference between Global Settings and INIT. In Global Settings, you allocate memory to the variables, and load any static resource needed. Fortunately, Petit Computer takes care most of it for you. Very little needed to be here. Some programming language requires you to load modules/libraries here as well.
INIT function deals with initializing the variables to start-up state. That means loading any custom screens if any. Backgrounds, Icons, and the like. This function gets called whenever the player quit to the title screen. It basically start fresh. If you have game states then you load that separately from this function. And yes, you want to have that special loading function, so you can override default graphics and provide the player with custom sprites and skin.
QUIT function basically says good-bye. There's not much here for Petit Computer. If you don't need anything, just leave it out, or just put out a good-bye message to the player.
The MAIN function will handle several types of cases:
- Infinite Loop
- Loop with Timer
- Loop with VSYNC
- Loop with Player input (wait)
- Loop with Player input (no wait)
- Loop with Player input + background process
- Loop with Player input + multi-thread
1. Infinite Loop
The first case is the simplest. You want the program to run forever, like in showing demo.
- @LOOP
- ?"Hello World"
- GOTO @LOOP
2. Loop with Timer
Sometimes, you want to have the program run for a certain length of time. Say, like a Timer. You can do it like this:
- 'TIMER PROGRAM BY HARRY HARDJONO
- SPSET 1,156,0,0,0,0
- SPOFS 1,-50,-50
- SPANIM 1,4,15
- SPSCALE 1,200
- @INIT
- CLS
- ?"HOW MANY SECONDS?"
- INPUT T
- IF 0>=T GOTO @END
- SPOFS 1,0,48,0
- SPOFS 1,224,48,T*60
- @LOOP
- IF (SPCHK(1) AND 1)==0 GOTO @END
- BEEP 28:WAIT 60
- GOTO @LOOP
- @END
- ?"TIME'S UP!"
- SPCLR 1
- BEEP 50
- WAIT 300
And that's it. The code before the INIT creates and sets the sprite. INIT is used to send the sprite across the screen, timed according to T variable. The loop then simply waits for the sprite to stop moving, and gave a "ding" sound when it's done. Also, sprite clean up is done at the END.
3. Loop with Player input (wait)
Let's modify the program a bit. We want to have a player input, and we want it to wait for each input. Let's say A to start the timer, B to set the timer, and X to end the program.
- @INIT
- CLS
- ?"HOW MANY SECONDS?"
- INPUT T
- IF 0>=T GOTO @END
- ?"A STARTS TIMER"
- ?"B SETS NEW TIME"
- ?"X EXIT"
- @LOOP
- VSYNC 1:B=BTRIG()
- IF (B AND 16) GOTO @TICK
- IF (B AND 32) GOTO @INIT
- IF (B AND 64) GOTO @END
- GOTO @LOOP
- @TICK
- SPOFS 1,0,48,0
- SPOFS 1,224,48,T*60
- @TOCK
- LOCATE 0,4:SPREAD(1),X,Y:?"TIME LEFT: ";FLOOR((224-X)*T/224);" "
- IF (SPCHK(1) AND 1) THEN BEEP 28:WAIT 60:GOTO @TOCK
- ?"TIME'S UP!":SPOFS 1,-50,-50:BEEP 50
- GOTO @LOOP
- @END
- ?"GOODBYE!"
- SPCLR 1:WAIT 300
If you notice, there's TICK and TOCK. Normally, I would put these on separate subroutine, but since I'm showing you how to do LOOP while waiting for user input, I simply group it all at once. Does it look like spaghetti code to you?
4. Loop with Player input (no wait)
Let's do one more improvement, and this time, we're going to do player input without waiting. Let's implement a PAUSE button. The truth is, it's very simple. Petit Computer, by default, does not wait for user input.
Here, we simply check if the sprite is moving. If so, then we stop it. Else, we start it.
- 'TIMER PROGRAM BY HARRY HARDJONO
- SPSET 1,156,0,0,0,0
- SPOFS 1,-50,-50
- SPANIM 1,4,15
- SPSCALE 1,200
- @INIT
- CLS
- ?"HOW MANY SECONDS?"
- INPUT T
- IF 0>=T GOTO @END
- ?"A STARTS TIMER"
- ?"B SETS NEW TIME"
- ?"X EXIT"
- ?"Y PAUSE"
- @LOOP
- VSYNC 1:B=BTRIG()
- IF (B AND 16) GOTO @TICK
- IF (B AND 32) GOTO @INIT
- IF (B AND 64) GOTO @END
- GOTO @LOOP
- @TICK
- SPOFS 1,0,48,0
- SPOFS 1,224,48,T*60
- @TOCK
- LOCATE 0,8:SPREAD(1),X,Y:?"TIME LEFT: ";FLOOR((224-X)*T/224);" "
- IF (BUTTON(0) AND 128) GOTO @PAUSE
- IF (SPCHK(1) AND 1) THEN BEEP 28:WAIT 60:GOTO @TOCK
- ?"TIME'S UP!":SPOFS 1,-50,-50:BEEP 50
- GOTO @LOOP
- @PAUSE
- IF (SPCHK(1) AND 1) THEN SPOFS 1,X,Y,0
- IF (BUTTON(0) AND 16) THEN SPOFS 1,224,48,FLOOR((224-X)*T/224)*60:GOTO @TOCK
- IF (BUTTON(0) AND 32) GOTO @INIT
- IF (BUTTON(0) AND 64) GOTO @END
- GOTO @PAUSE
- @END
- ?"GOODBYE!"
- SPCLR 1:WAIT 300
Simple as that. We simply use the variable values from TIME LEFT to stop the sprite where it stands, and starts it in according to TIME LEFT. There's a trick here, that we use BUTTON(0) instead of BTRIG. We do that because of WAIT 60 that we have will cause BTRIG signal to get lost. BUTTON(0) will read the input continuously. Press A to restart the timer.
Petit Computer Programming can be so easy! Next, we'll examine loops with background processes.
