Speaking as someone with some experience in programming (with UI window management), the actual implementation of this on a code level must have been very interesting. Some light explanations: - Window size and position are measured in 3 sets of parameters: *Position* (X,Y) is relative to the desktop origin (in the upper-left). *Width and height* are often the _total_ window size (including OS-level elements like border thickness and application title bar), but there's also an *_interior_** width/height* inside which the app has full control of the rendering. - Crucially, in interior window space, position (0,0) refers to the upper-left corner of the window's interior space, so while it's a simple matter to resize the right (or bottom) edges without affecting the apparent position of anything (inside the window) relative to the whole screen, resizing the left/top edges without everything on the window just shifting with it requires monitoring the windows' resize events and adjusting its rendering "camera" position to compensate. Which is not truly difficult to _do_ so much as it is tricky to _keep consistent._ - Most applications are designed with just one ("main") window in mind. It is generally unusual to see an application spawning multiple windows, in part because user input is directed to a single "active" window -- meaning the game likely needed a unified input handler duplicated across all windows to ensure that player (keyboard) input is received consistently.
Thank you for bringing a new and cool perspective to the difficulty behind programming a game like this! I wish I knew how to program and do things like this, but I’ll leave that up to people who know a lot more about it like you 😂
@@SmartShenanigans _(shrug)_ Well, I haven't touched actual application programming in years, but it's definitely one of those things that, once learned, you never forget. For example, I had one application with various toolbars placed along the edges of its windows, but I didn't like the IDE's (engine's) built-in way of providing that, so I resorted to positioning them myself ... the code was a total mess but at least it worked the way _I wanted it to._
lmao theres a pink cursor boss that literally takes a screenshot of you getting hit by a bullet or enemy and saves it in a folder named cringe compilation😂😂😂
I'm not going to make a tutorial video as that is not the style of content that I produce, however, all you have to do is download the zip file from the itch.io website that I linked in the description and unzip it to run the game!
Speaking as someone with some experience in programming (with UI window management), the actual implementation of this on a code level must have been very interesting.
Some light explanations:
- Window size and position are measured in 3 sets of parameters: *Position* (X,Y) is relative to the desktop origin (in the upper-left). *Width and height* are often the _total_ window size (including OS-level elements like border thickness and application title bar), but there's also an *_interior_** width/height* inside which the app has full control of the rendering.
- Crucially, in interior window space, position (0,0) refers to the upper-left corner of the window's interior space, so while it's a simple matter to resize the right (or bottom) edges without affecting the apparent position of anything (inside the window) relative to the whole screen, resizing the left/top edges without everything on the window just shifting with it requires monitoring the windows' resize events and adjusting its rendering "camera" position to compensate. Which is not truly difficult to _do_ so much as it is tricky to _keep consistent._
- Most applications are designed with just one ("main") window in mind. It is generally unusual to see an application spawning multiple windows, in part because user input is directed to a single "active" window -- meaning the game likely needed a unified input handler duplicated across all windows to ensure that player (keyboard) input is received consistently.
Thank you for bringing a new and cool perspective to the difficulty behind programming a game like this! I wish I knew how to program and do things like this, but I’ll leave that up to people who know a lot more about it like you 😂
@@SmartShenanigans _(shrug)_ Well, I haven't touched actual application programming in years, but it's definitely one of those things that, once learned, you never forget.
For example, I had one application with various toolbars placed along the edges of its windows, but I didn't like the IDE's (engine's) built-in way of providing that, so I resorted to positioning them myself ... the code was a total mess but at least it worked the way _I wanted it to._
That's totally fair! I get not liking how something is in the built-in form and just redoing it yourself lol
W game + W video
It really is a W game! And thanks for checking out the video!
you didn't even manage to kill the first boss out of 6
now v3 gonna kill us
Unfortunately, I’m not the best at bullet hells, but this game was far too cool to pass up lol
lmao theres a pink cursor boss that literally takes a screenshot of you getting hit by a bullet or enemy and saves it in a folder named cringe compilation😂😂😂
Yoooo that’s actually hilarious 😂😂😂😂
How to install please make a tutorial
I'm not going to make a tutorial video as that is not the style of content that I produce, however, all you have to do is download the zip file from the itch.io website that I linked in the description and unzip it to run the game!
theres now a steam version with more content for 5$
@@eb924yes i have it
woah
It was such a cool game! Definitely gonna have to play more in my free time
@@SmartShenanigans I bet