Differences

This shows you the differences between two versions of the page.

--- notes:cprog:fall2024:projects:fwg1 [2024/03/04 13:04] – created - external edit 127.0.0.1
+++ notes:cprog:fall2024:projects:fwg1 [2024/10/24 03:46] (current) – [bounds checking] mwinter4
@@ Line 12: / Line 12: @@
 ====gamepad====
+By default Vircon32 uses the keyboard as the gamepad
+  * D-Pad: Arrow keys
+  * L/R Bumpers: 'Q' and 'W' keys
+  * Y/X Buttons: 'A' and 'S' keys
+  * B/A Buttons: 'Z' and 'X' keys
+To use player inputs you need to include [[https://www.vircon32.com/api/input.html|input.h]]
+gamepad_direction provides a simple way to read and store player D-Pad inputs
+<code>
+//Initialize variables used to store player input
+int xDirection;
+int yDirection;
+//The addressof operator is used because the gamepad_direction methods changes the value of its inputs
+gamepad_direction(&xDirection, &yDirection);
+</code>
 =====structures=====
+The Vircon32 c compiler uses different syntax to gcc, and has more limitations placed on structures. For more information see the [[https://github.com/vircon32/Vircon32Documents/blob/main/Guides/English/PDF%20documents/Guide%20-%20Guide%20for%20the%20C%20compiler.pdf|quick guide]]
+<code>
+//declare structure
+struct exampleStructure
+{
+    int myVariable;
+    int myValue;
+};
+//declare a variable of type exampleStructure
+exampleStrucutre somethingUseful;
+//assign values to each property of variable
+somethingUseful.myVariable = -30;
+somethingUseful.myValue = 99;
+</code>
 =====bounds checking=====
+Bounds checking is the process of checking to make sure a variable remains bounded by some defined limit. In our case, and as is the case for many games, we want to check to see if the character is going to coordinates off-screen so that we can regain the player's perspective and ensure they can still see the playable character.
+To bound check, we can simply view the coordinates of our main player character to determine if they are at coordinates that rest outside of the screen height and width. Here is an example of how one might horizontally check bounds and wrap the player around to the opposite side:
+<code>
+void ourFunction(player* p){
+    if(p->position_x > screen_width)
+    {
+        p->position_x -= screen_width;
+    };
+}
+</code>
+This assumes that we've passed in a pointer to our player structure that we will call p for this function.
+There is also the assumption that there is a member variable of this structure called <wrap hi>"position_x"</wrap> that is the X coordinate of the player as it is rendered on the screen. If we reach the <wrap hi>screen_width</wrap>, which would be the very right of the screen, then we render the player at the lowest x coordinate within our bounds, 0.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools