Skip to main content

Posts

Showing posts from December, 2019

(VIII) Collisions and strings: dim as string & draw string

G'day everybody! In this entry we will see the collisions, and we will use a concret one wich is the perfect superposition between two elements, as it used for pac-man and the ghosts. We have a perfect superposition when te coordinates of two elements are the same, same value for x axis and same value for y axis. Take a look at the new code of the day: Let me explain the new keywords used: dim as string  to declare a new variable that will contain an string, an string is delimited with an initial " and a final ". draw string  to draw a string on the screen at the point indicated. The sintaxis is draw string (x,y),string in our case draw string (0,h/2),message When we execute this code we can move the white square toward the other ones and the message in the screen will remember the color with which square the last collision occurs. Today's code and concepts are very important because we have an square with controlled interacti

(VII) Movement: arrow keys, and, +=, -=, variable coordinates

Howdy everybody! Take a look at the new code of the day: In this code we have defined new keyboard scan codes for the arrow keys, see it in the DECLARATIONS as constants and declare variables to control if the keys are pressed or not, like we did it with key escape. Here x and y that are the coordinates of the white square will turn into variables because we will move this square then the value of the coordinates will be variable. When we DO UPDATE this time we will check also the four possible arrow keys and checking not to go with our white square outside our screen, otherwise the square will hide, you can prove it. Notice that the condition is multiple, using and to check that both conditions are true at the same time to change the value of the corresponding variable. We increment or decrement x or y with 1 (1 pixel), to go up y-1, right x+1, down y+1 or left x-1. This way: To increment we use the form variable+=amount of increment, for exemple x+=1 To de

(VI) Frame control & locking the screen while drawing: screensync, cls, screenlock, screenunlock

Hiya everybody! Take a look at the code of the day: Let me explain the new keywords used: screensync  is the key to take the number of frames per second under control because this instruction waits until next refresh of the screen, usually 60 times per second known as 60 fps. After this we will draw our screen. cls  to CLear the Screen and draw from zero the new state of the game. screenlock  to lock the screen to hide it while we are drawing. screenunlock  to unlock the screen to show the new drawed screen. Is very important to respect that we have to draw inmediately after the screensync and remember that between screenlock and screenunlock you have to draw, nothing else to do this part of the code as fast as possible. How is the structure? more and more accurate every time: DESCRIPTION DECLARATIONS INITIALIZATIONS GAME LOOP INPUT DO UPDATE DRAW screensync screenlock cls ... screenunlock FREE UP CPU TIME sleep 1,1 ENDING This is e n

(V) Game loop, variables, dim as boolean, if then else, multikey, false, true, do loop until

Hey everybody! Take a look at the code of the day: The result of execute our new code will be the same as the obtained with the code of the last entry but you must press Esc key to exit: An screen to play with 400 pixels of width and 300 pixels of height and four squares of 32x32 pixels one in each corner. The white square is painted or filled with same color. The screen is being draw again and again and again until you press Esc key. Let me explain the new keywords used: dim as boolean  as const as but with dim we are telling that the label (in our case finish and kescape) will have a variable value. In the case of boolean this value can be false or true. do loop until to make a loop that will repeat the code inside the instruction until the condition after until is resolve to true. if then else  to execute the code inside the instruction if the condition is resolve to true, else to execute an alternate code if the condition is  not resolve to true. multikey t

(IV) Draw some colored squares: line -step

Hello everybody! Let's enrich our first code drawing four colored squares. This is the result of our new code: An screen to play with 400 pixels of width and 300 pixels of height and four squares of 32x32 pixels one in each corner. The white square is painted or filled with same color. Let me explain the new keywords used: line  to draw a line between a point referenced with its coordinates (value in axis x,value in axis y) and an increment/decrement in pixels form this point -step(inc/dec in axis x,inc/dec in axis y) and two parameters separated by comma, the first is the color and the second is optional, if you used it you can put a b that means box or bf that means box filled. Try changing color values from 0 (black or transparent) to 15 (white) and experiment with the parameters. This is e nough by now, in t he next entry we will make great advance learning a change in the structure of the code because the famous game loop. Contact me for any question,

(III) Make an screen to play: ', const as integer, screenres, sleep & end

Come on everybody! Let's see our first code to make an screen to play. Let me explain the keywords used: '   t o add comments to the code, very useful to understand even the code made by ourselves. Used alone in a row or at the end of an instruction. const as integer to declare labels as integer numbers that contain constant values, non modifiable along the program. In this case w and h are constants. We must separate different consts with comma. screenres to do an screen to play, we have to tell two parameters the width and the height of the screen. We must separate parameters with comma. sleep to wait until a key is pressed to see the screen that otherwise will close too fast. end to end the program.  And the structure of this code not too far from the structure of a larger one: DESCRIPTION DECLARATIONS INITIALIZATIONS Main code ENDING In FBIde you can run the code pressing function key F5 or clicking Quick run icon This is the result of our first

(II) Download & setup FreeBASIC's IDE FBIde

Hi everybody! If you use Microsoft Windows on your computer you can download FBIde from SourceForge in this link:  https://sourceforge.net/projects/fbide/files/ Go to fbide 0.4 folder and then fbide 0.4.6 r4  folder and download the zip file with the name  FBIde0.4.6r4.zip . Note: 0.4.6 r4 is the last version while doing this blog entry. Now decompress downloaded file in the path you desire. Me I decided to use my Desktop, beside my FreeBASIC compiler and help folders. Go into  FBIde0.4.6r4  folder and execute the application  fbide Click Yes in the message window. And search fbc application inside your FreeBASIC's compiler folder to open it. Go to View/Settings to Choose your Theme for the editor, I like obsidian theme. Add some new Keywords in Group 2 . Choose the path for FreeBASIC Help file (.chm) downloaded in the previous entry of this blog. Remember to click OK to submit the changes. This is e nough by now, in the next entry we will

(I) Download FreeBASIC compiler & help

Welcome everybody! You can download FreeBASIC from SourceForge in this link:  https://sourceforge.net/projects/fbc/files/ If you use Microsoft Windows on your computer you can go to Binaries - Windows folder and download the zip file with the name FreeBasic-1.07.1-win32.zip that will run both 32 and 64 bits systems. Note: 1.07.1 is the last version while doing this blog entry. We will also download the help file going back and entering the folder Documentation and downloading the zip file FB-manual-1.07.1-chm.zip Now decompress both downloaded files in the path you desire. Me I decided to use my desktop. Go into FreeBASIC-1.07.1-win32  folder and create a Projects folder that we will use to save our programs and their resources. This is enough by now, in the next entry we will download and setup our IDE to write and run our programs. Contact me for any question, see you! Go to the next entry