I want to start game programming and i want to be able to read these differen types of languages before i go to college so i don t look like a idiot.
its a blue light. and the temp. doesnt stay real high- maybe 80 degrees. would it hurt to leave it on all day long? my boyfriend thinks i should just leave it on for 12hrs. what do you think?
i have a heat pad under the tank right under his hut. so thats a warm spot for him. but i have a light as well.
oh- for the rude responder- we ve had this snake for 2yrs. and hes beautiful. its not nice to speak before you know what you are talking about.
Shoulld i belive this http://www.youtube.com/watch?v=zP2bjzvIPV8
I m having some trouble with Python- and am not sure if I ran in to a bug or not. I have an update() method on a class called Game. The following code doesn t get to the event loop unless I uncomment the print statement. I uncomment print- and it gets there just fine. Everything is tabbed properly- but yahoo answers strips the tabs.
def update(self):
<tab>#print "anything" #then of course it continually prints this.
<tab>for event in pygame.event.get():
<tab><tab>if (event.type == KEYDOWN):
<tab><tab><tab>if pygame.key.name(event.key).upper() == "Q":
<tab><tab><tab><tab>labelPosx += 10
Here are the imports:
import pygame
from pygame.locals import *
import gameEngine
Any help is appreciated. It seems like a bug to me because you shouldn t have to have a print statement to be able to run the event loop.
Any help is appreciated.
Thanks!!
I ve tried that actually... What I had at one time was:
def update(self):
<tab>#print "anything" #then of course it continually prints this.
<tab>for event in pygame.event.get():
<tab><tab>print "made it here"
<tab><tab>if (event.type == KEYDOWN):
<tab><tab><tab>if pygame.key.name(event.key).upper() == "Q":
<tab><tab><tab><tab>labelPosx += 10
I had a made it here print line inside the event loop. If the first print is commented out- it won t make it to the second print statement. Once I uncomment- it displays both. That s why I was thinking it was a bug.
No comments:
Post a Comment