[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pygame] Documentation Query/Bug Report
On Wed, Jan 23, 2002 at 10:48:00AM +0100, wijgerden@hetnet.nl wrote:
> My little test shows that given an 3x3 img like this (ascii muck up):
Can't reproduce this, but your sample code looks like you made a standard
error:
> -x-
> o+-
> ---
>
> # Try to flip around the x-axis
> imgA = pygame.transform.flip(img, 1, 0)
Here you flip 'img' and the flipped surface is stored in 'imgA'
> # Try to flip around the y-axis
> imgB = pygame.transform.flip(img, 0, 1)
Here you again flip 'img' and the flipped surface is stored in 'imgB'
> gives this imgB (ascii muck up again):
>
> ---
> o+-
> -X-
Now consider what you've done was only flipping the original image at
the Y axis. And the result is obviously correct
> Now, I think this doesn't meet the documentation.
It does :)
> Isn't imgA flipped around the Y-axis and ImgB around the X-axis? Or is this again according to math standards?
imgA is not flipped at all. neither is imgB flipped. You only flipped
'img' twice.
> Note that I use the original image img in all cases.
Note that you could have noted that everything works correctly in that case :)
--
Raiser, Frank aka CrashChaos
IRC: irc.openprojects.net #pygame
- "It looks worse than you can imagine!"
- "I can imagine some pretty bad things!"
- "That's why I said *worse*!"
-- (Terry Pratchett, Moving Pictures)
____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org