Video Game Blog
March 15, 2019
Now that I've got the map projection working again, I'm going to baby-step through individual things that need to get changed to make the new system work. First thing on the list is to convert the old tile-detecting code for the Cursor so that its measurements on based upon percentages instead of pixel-specific.
The Square Map of course is super simple...it's already based upone simple division of a simple rectangle shape. No need to work on that...
The other Tile types though...those shapes still sit within a rectangle shape, but have to have the edges of their various angles accounted for to see if the User meant to be targetting a Tile adjacent that overlaps rectangles...
I've implemented and tested against the 32-pixel Tile set to see if the Cursor is working. Because the system works on percentage-math, the Cursor is a little jumpy while you move the cursor. If you're intent at aiming in the center of any of the Tiles though, it is spot on.
I'll test against the other Tile sets later after I've implemented the Screen Scaling System. I suspect that the larger Tiles will be less jumpy due to more pixels per rectangle to test against, leaving more room for the x- y- of the Mouse to move through without hitting more than one test zone at a time.
As I am coding, I see things that I know I want to address as I work on one thing or another and I try to make mental note to come back to it after I finished what I'm working on. Wouldn't be a problem if I were able to put in a lot of hours per day, to stop only when I finish these things done...
But since I am not able to work straight through, I'm now leaving myself comments within the code to tell me to work on this or that. Even then, I have to go back and find the things to do (programmers comment it as "TODO:..."). This is fine, as all I have to do is search for the "TODO" word and I can be taken to it right away. But, I am thinking...wouldn't it be more professional if I create a document that would talk about the things that have been addressed, how the new changes affect the old stuff, plus what other changes need to be done to make desired results to happen. So, I'm thinking to also keep a journal for myself that details these things so that I get a "full story" about what's going on versus the small notes within the code that may be only of partial help in understanding.
Keeping a blog is one thing, written at a level of comprehension that non-programmes can keep up with. But my journal idea, practically a "technical journal" could be seen by other programmers and could pick up the work right behind where I left off.
Well, time for me to get to work. I'll have to put this away...(dang it...)
