On Mon, Jul 25, 2011 at 4:53 PM, DR0ID wrote:
> On 25.07.2011 11:13, Mac Ryan wrote:
>
>> Hi and thank you for your answer.
>>
>>I think I failed to explain myself properly. What I meant with
>> my question is that I have been surprised that the drawing of sprites
>> happens **calling sur
On 25.07.2011 11:13, Mac Ryan wrote:
Hi and thank you for your answer.
I think I failed to explain myself properly. What I meant with
my question is that I have been surprised that the drawing of sprites
happens **calling surface.blit(sprite.image, sprite.rect)** instead than
**calling s
On Mon, 25 Jul 2011 06:45:44 +0100
René Dudfield wrote:
> There are things like z-order as well, which make drawing in the
> group the way to do it. If you did Sprite drawing, then each Sprite
> would first need to talk to the other sprites in order to know when
> to draw.
Hi and thank you for
Hey,
it can seem a bit weird that drawing is done in the Group, and not the
Sprite.
However, since you will nearly always be drawing all the sprites every time,
then it makes sense to draw them in the group.
There are things like z-order as well, which make drawing in the group the
way to do it.
Hi all,
I'm pretty new to pygame (although I have good experience with python)
and this is my first message on the list. Bear with me if what I am
about to ask has been already discussed.
While working around my first program, I realised that while each
sprite has an update() function, it's drawi
