On Tue, Jan 13, 2009 at 6:07 PM, Brian Fisher br...@hamsterrepublic.com wrote:
Well in that case, it seems that knowing the size value passed to the
constructor is only half of what you need to make a font at twice the size
of the original.
You are not missing anything Brian, if facts you are
The acceleration is changed once a second (for meters/second) this
leads to very jumpy movement. I need to add a way to check how long it
takes the program to loop and multiply the acceleration by that much.
(I think)
A quick way, is to do something like this:
This allows you to define
On, Mon Jan 12, 2009, Lenard Lindstrom wrote:
Color equality was an oversight I corrected in Pygame 1.9.0.
In pgreloaded it's implemented differently, so watch your comparisions
in case you use it.
Regards
Marcus
pgpywpjIPxaxa.pgp
Description: PGP signature
How so, or what do I need to watch? Meaning is it safe for now to do?:
if self.color == pygame.Color(red): print 'same color!'
On Wed, Jan 14, 2009 at 5:44 AM, Marcus von Appen m...@sysfault.org wrote:
On, Mon Jan 12, 2009, Lenard Lindstrom wrote:
Color equality was an oversight I corrected
On, Wed Jan 14, 2009, Jake b wrote:
How so, or what do I need to watch? Meaning is it safe for now to do?:
if self.color == pygame.Color(red): print 'same color!'
In the recent pygame versions you can do something like:
if color == 0xff: print it's red!
Comparing a color to a string
On Tue, Jan 13, 2009 at 06:44:10AM -0600, Jake b wrote:
I'm learning about doctest, and unittests. Now if I create a file, like
pygame/test/rect_test.py , is there and easy way to import the project in
its parent directory?
Make sure it's in sys.path, then import using the absolute package
High Marcus,
I agree that comparing a color to a string was not a good idea. That can
go as 1.9.0 is still pre-alpha. For backwards compatibility comparison
with a tuple will remain valid in Pygame 1.9.
Lenard
Marcus von Appen wrote:
On, Wed Jan 14, 2009, Jake b wrote:
How so, or
2) Do you have two seperate unittests ? (A) One is ran every time source
files are compiled, and a second, (B) slower one is ran at a longer
interval
for slow tests ?
Such separation is rarely necessary.
Something I started on, requires rendering. It's not a huge delay, but I
don't want
Lenard Lindstrom le...@telus.net:
High Marcus,
I agree that comparing a color to a string was not a good idea. That
can go as 1.9.0 is still pre-alpha. For backwards compatibility
comparison with a tuple will remain valid in Pygame 1.9.
Absolutely - one of the main issues was (and is) the
On Wed, Jan 14, 2009 at 10:57 AM, Jake b ninmonk...@gmail.com wrote:
2) Do you have two seperate unittests ? (A) One is ran every time source
files are compiled, and a second, (B) slower one is ran at a longer
interval
for slow tests ?
Such separation is rarely necessary.
Something I
explicitly. That cookbook example sounds like it is less about
compiling, and more
of a way to implicitly run tests when the application runs.
Right. it auto-runs your tests when the code is compiled.
are pretty much inherently checking for compiler errors, so there is no need
to test for
Hi,
I'm working on a game SDK (http://code.google.com/p/scrollback) and
things are going more or less smoothly, but I would like to experiment
with Pgu to see if/how I can make it work with my SDK. Unfortunately,
Pgu tools and examples keep raising weird exceptions in relation to
trying to access
12 matches
Mail list logo
