[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] erratic behavior with 'display.update(Rect)'

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] erratic behavior with 'display.update(Rect)'
From: Tom Rothamel <tom@xxxxxxxxxxx>
Date: Tue, 14 Jul 2015 00:34:14 +0000
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Mon, 13 Jul 2015 20:34:29 -0400
In-reply-to: <CAFKYrxqYJTuyAqf_zySARFT=Wv=RvB=1N0x76gwheEGLR4Sn_Q@xxxxxxxxxxxxxx>
References: <CAFKYrxqYJTuyAqf_zySARFT=Wv=RvB=1N0x76gwheEGLR4Sn_Q@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

On Mon, Jul 13, 2015 at 6:54 PM tom arnall <kloro2006@xxxxxxxxx> wrote:

If display.update()' doesn't work with OPENGL, what do you use to
update just one area of the display?

There isn't a way to update a portion of the display using OpenGL. OpenGL expects you to redraw the screen from scratch every frame, and then flip to the next frame.

How are you drawing to the screen? Are you using GL calls? Or pygame blits to the screen surface? The later doesn't work with OPENGL.

Follow-Ups:
- Re: [pygame] erratic behavior with 'display.update(Rect)'
  - From: Ian Mallett

References:
- [pygame] erratic behavior with 'display.update(Rect)'
  - From: tom arnall

Prev by Author: Re: [pygame] Which project is actually pygame2?
Next by Author: Re: [pygame] pygame to android
Previous by thread: [pygame] erratic behavior with 'display.update(Rect)'
Next by thread: Re: [pygame] erratic behavior with 'display.update(Rect)'
Index(es):
- Author
- Thread