So it looks like I’mna have to make a GUI class instead of trying to work without one, my understanding of locals vs globals is certainly not nearly complete enough, and it just seems easier.
Unfortunately I’m going to use threading instead of multi threading or whatever module is builtin on top of it, just because it it simple enough for now, and I really just need to get a good grip on what it means to have threads.
I’m trying to get a GUI going with my game, mostly for debugging and that kind of stuff, but I ran into the very common issue where my game hangs on the initialization of tkinter. So I had to look into threading, which is apparently very easy in Python.
I’m using the Programming Python books, by Mark Lutz (O’REILLY pub) and it’s got a fairly good look at the basic concepts so far. Here’s something I wrote for myself, that I used to get a decent handle of threads, using the threads module in py2.6. What it does it changes the color of the background in the pygame window, and when you open the tkinter window, you can set that color in real time, without any hangs. It’s pretty neat, and I’m looking forward to adding it into my main game.
I’m still sorta getting the hang of lambdas only because it does seem to look right to me, even if I use them properly. I’ve got a line that goes:
root.bind('<Return>', (lambda event: printEnt(ent)))
And I don’t know why
event
isn’t given properly and there’s no exception raised…
Oh well, there’s always tomorrow.
I guess I got a bit hasty, and instead of doing the responsible thing, I just erased some complicated forward thinking functions I had implemented, and now everything is going to be dealt with as if it was normalized. I had to change a bunch of code, but the entire code base is still less than 1k lines, so it wasn’t too too bad.
Currently trying to integrate a new window/frame with tkinter so I can monitor certain stats, debug or otherwise, without printing ’em. Hopefully I’ll figure it out, otherwise I’m sure pyGame has some sort of window option.
Well this is unfortunate. I’ve realized that I have neglected to use either normalized vectors or un-normalized vectors all over. So essentially I’m always scrambling to figure out what a given vector really is.
Not to mention that I’ve got my code split into components within itself, that is a unit has itself, then under it, it has its AI and Shooter component. I’m mixing and matching name variables and methods everywhere, it’s getting very easy to get lost.
I imagine if I ever get around to rewriting, I’m going to have to create a class for vectors, with all the methods I can think of, such as length, distance, dot, cross product, atan and all that kind of stuff.
I’m trying to get a cone of vision going, but it’s all zany sized, which makes me think it’s the un/normalized vectors messing with me. I can’t be sure.
Thinking about putting up a link to this blog soon though.
Lines 776, files 1
Alright, so I’m at a point where I’ve begun showing it off to a few friends. It’s cool enough to see for my first project. It’s got just enough to be a minimal app. It’s basically moving and shooting still targets now.
What I’ve got is :
frame_count += 1
if frame_count % 15 == 0:
t1 = time.clock()
frame_rate = 15 / (t1-t0)
t0 = t1
What I’m looking to do now is add a basic AI, where it moves for a second and aims for another 1/2, then decides to fire if it can see an enemy.
Balls though, my math has never really been that great, but it’s sure as shit challenging using all the sine and cosine and atan2 stuff.
I’m also struggling with using PyGame’s Rects properly.