Re: FULLSCREEN and DOUBLEBUF

2018-06-12 Thread Greg Ewing
Paul St George wrote: I had considered meddling with the config.txt to try to enable* HWSURFACE but from what you say, this is unnecessary. I don't really have much idea what effect HWSURFACE would have, if any. It will certainly depend a lot on your hardware and drivers. My suggestion would b

Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-12 Thread Paul St George
Dennis Lee Bieber wrote: Both may be dependent upon the actual hardware graphics board and the drivers for said board. On 11/06/2018 01:47, Gregory Ewing wrote: My guess is that if your surface is not fullscreen or is not a hardware surface, then you're always drawing into an ofscreen bu

Re: FULLSCREEN and DOUBLEBUF

2018-06-10 Thread Gregory Ewing
Dennis Lee Bieber wrote: Both may be dependent upon the actual hardware graphics board and the drivers for said board. My guess is that if your surface is not fullscreen or is not a hardware surface, then you're always drawing into an ofscreen buffer that gets copied to the screen when

Re: Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-10 Thread Paul St George
Paul St George wrote: So... print pygame.display.get_surface() gives and print screen.get_flags() gives -2147483648 To recap: this thread started with a question. How do I know whether DOUBLEBUF has been set with: screen = pygame.display.set_mode((720,480), pygame.DOUBLEBUF | pyg

Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-10 Thread Peter Otten
Paul St George wrote: > So... > > print pygame.display.get_surface() > gives > > > and > print screen.get_flags() > gives > -2147483648 > To recap: this thread started with a question. How do I know whether > DOUBLEBUF has been set with: > > screen = pygame.display.set_mode((720,480

Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-10 Thread Paul St George
To recap: this thread started with a question. How do I know whether DOUBLEBUF has been set with:     screen = pygame.display.set_mode((720,480), pygame.DOUBLEBUF | pygame.FULLSCREEN) On 09/06/2018 22:04, Mark Lawrence wrote: On 09/06/18 20:31, Paul St George wrote: print pygame.disp

Re: FULLSCREEN and DOUBLEBUF

2018-06-09 Thread Mark Lawrence
On 09/06/18 20:31, Paul St George wrote:     print pygame.display.get_surface() gives and     print screen.get_flags() gives -2147483648 The lists of flags at and

Re: FULLSCREEN and DOUBLEBUF

2018-06-09 Thread Richard Damon
On 6/9/18 3:31 PM, Paul St George wrote: > So... > >     print pygame.display.get_surface() > gives > > > and >     print screen.get_flags() > gives > -2147483648 > > The lists of flags at > > and >

Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-09 Thread Paul St George
On 08/06/18 09:00, Paul St George wrote: Excellent. Now I know what to do in this instance and I understand the principle. I hesitantly tried this: screen = pygame.display.set_mode((720,480), pygame.FULLSCREEN | pygame.DOUBLEBUF) Hesitantly because I expected the *bitwise or operator

Re: FULLSCREEN and DOUBLEBUF

2018-06-08 Thread Rhodri James
On 08/06/18 12:41, Darren Pardoe wrote: On Friday, 8 June 2018 12:24:26 UTC+1, Rhodri James wrote: On 08/06/18 09:00, Paul St George wrote: PS: it's generally considered polite not to top post on this mailing list. -- Rhodri James *-* Kynesim Ltd Rhodri, Guys, I have always top posted even t

Re: FULLSCREEN and DOUBLEBUF

2018-06-08 Thread MRAB
On 2018-06-08 12:41, Darren Pardoe wrote: On Friday, 8 June 2018 12:24:26 UTC+1, Rhodri James wrote: On 08/06/18 09:00, Paul St George wrote: PS: it's generally considered polite not to top post on this mailing list. -- Rhodri James *-* Kynesim Ltd Rhodri, Guys, I have always top posted even

Re: FULLSCREEN and DOUBLEBUF

2018-06-08 Thread Darren Pardoe
On Friday, 8 June 2018 12:24:26 UTC+1, Rhodri James wrote: > On 08/06/18 09:00, Paul St George wrote: > PS: it's generally considered polite not to top post on this mailing list. > > -- > Rhodri James *-* Kynesim Ltd Rhodri, Guys, I have always top posted even though most editors start with the

Re: FULLSCREEN and DOUBLEBUF

2018-06-08 Thread Rhodri James
On 08/06/18 09:00, Paul St George wrote: Excellent. Now I know what to do in this instance and I understand the principle. I hesitantly tried this:     screen = pygame.display.set_mode((720,480), pygame.FULLSCREEN | pygame.DOUBLEBUF) Hesitantly because I expected the *bitwise or operator*

Re: Re: FULLSCREEN and DOUBLEBUF

2018-06-08 Thread Paul St George
rge wrote: This is both a narrow question about some code and a more general question about syntax in Python Using the Pygame modules, I want to set both FULLSCREEN and DOUBLEBUF I can use screen = pygame.display.set_mode((screen_width,screen_height),pygame.FULLSCREEN) to set a FULLSCREEN di

Re: FULLSCREEN and DOUBLEBUF

2018-06-07 Thread Mark Lawrence
On 07/06/18 18:12, Paul St George wrote: This is both a narrow question about some code and a more general question about syntax in Python Using the Pygame modules, I want to set both FULLSCREEN and DOUBLEBUF I can use screen = pygame.display.set_mode((screen_width,screen_height

Re: FULLSCREEN and DOUBLEBUF

2018-06-07 Thread Chris Angelico
On Fri, Jun 8, 2018 at 3:12 AM, Paul St George wrote: > This is both a narrow question about some code and a more general question > about syntax in Python > > Using the Pygame modules, I want to set both FULLSCREEN and DOUBLEBUF > > I can use > screen = > pygame.displa

FULLSCREEN and DOUBLEBUF

2018-06-07 Thread Paul St George
This is both a narrow question about some code and a more general question about syntax in Python Using the Pygame modules, I want to set both FULLSCREEN and DOUBLEBUF I can use screen = pygame.display.set_mode((screen_width,screen_height),pygame.FULLSCREEN) to set a FULLSCREEN display Or