[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] question about scrolling the world
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] question about scrolling the world
- From: "Brian Fisher" <brian@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Mar 2008 10:34:42 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Thu, 20 Mar 2008 13:34:46 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=nDFig05A5yDJ//+xeZEEViCDg/zA4IZAZZzP7s+RbFA=; b=CWb9dtMEFOUpf8paYOm0UByHRHmA75UdLUy9iWAGwj5MclUG1SXPJWlZtJJG+nWMMEkbPKBdiqxKW9E2U8e++vtusD+ssJ2CgQNqwaKGAcLrTorBg35+sfHtj+EqPERobbfgq/lU5oOx11Kh8hqqUekWbCsR1vW2QPWaOLDpwlI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ilmzJH0eAL3vLvQHIL3l2X4Ht0vcaZ9Kmi3GgLQPCxvAz7rNhfx4W+qce1X2DMv+9b5NCPzuZiRt1m1ETn6ZXPY6p43RQjE0fBjqI3YQcKbdhtGzDOvFxsC462A2JOpHquZS37eHvHigQTM+VEJMx1mbb9Os4KMzlmgMLpiN9BM=
- In-reply-to: <20080320132903.7042c386@xxxxxxxxxxxxx>
- References: <20080320132903.7042c386@xxxxxxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
surface.blit should clip just fine in the case you mention.
On Thu, Mar 20, 2008 at 10:29 AM, Michael Fiano <michael.fiano@xxxxxxxxx> wrote:
> Being new to game design, I'm wondering if it's a good idea to load the
> whole map data and blit the huge surface to the screen so that a lot of
> it is off-screen, then moving it with an offset value for the scrolling.
> Is the cpu going be busy updating off-screen pixels? Is this
> inefficient? I can't think of an easier way to do it for my existing
> code. Thanks.
>