Thanks Devon, Claudio and René, I'll keep in mind your advices to try to make the game structure cleaner.
Regards,
PabloOn Sat, Sep 19, 2009 at 5:30 PM, Devon Scott-Tunkin <djvonfunkin@xxxxxxxxx> wrote:
A state machine or stack is a usual way to do it, where each state/scene has its own update stuff and event handling and the pygame loop just uses the current scene.
--- On Sat, 9/19/09, Pablo Moleri <pmoleri@xxxxxxxxx> wrote:
> From: Pablo Moleri <pmoleri@xxxxxxxxx>
> Subject: [pygame] Standard methodology for different game screens
> To: pygame-users@xxxxxxxx
> Date: Saturday, September 19, 2009, 1:13 PM
> Hello,
>
> I'm going through a game code
> written in pygame, the game shows different screens:
> - an introduction
>
> - a menu
> - and then it enters to different game modes.
>
> For each of these parts there's a different pygame
> loop, which doesn't seem right.
> I would like to know if there's a standard way to use
> pygame in this scenario.
>
>
> Thanks in advance,
> Pablo
>
>
>