From: <mth...@us...> - 2010-03-25 01:35:18
|
Revision: 11365 http://openmsx.svn.sourceforge.net/openmsx/?rev=11365&view=rev Author: mthuurne Date: 2010-03-25 01:35:11 +0000 (Thu, 25 Mar 2010) Log Message: ----------- Use software surface for Dingux. We use a software surface in the default case too, but maybe that will change in the future. Also, the added comment documents why we have to use a software surface. Modified Paths: -------------- openmsx/trunk/src/video/SDLVisibleSurface.cc Modified: openmsx/trunk/src/video/SDLVisibleSurface.cc =================================================================== --- openmsx/trunk/src/video/SDLVisibleSurface.cc 2010-03-24 00:42:33 UTC (rev 11364) +++ openmsx/trunk/src/video/SDLVisibleSurface.cc 2010-03-25 01:35:11 UTC (rev 11365) @@ -31,6 +31,14 @@ // the work surface to the display surface (the HW blitter on GP2X is // fast enough). int flags = SDL_HWSURFACE; // | SDL_DOUBLEBUF; +#elif PLATFORM_DINGUX + // Double buffering hangs openMSX (tested 2009-07-22). + // The Dingoo seems to have a hardware problem that makes it hard or + // impossible to know when vsync happens: + // http://www.dingux.com/2009/07/on-screen-tearing.html + // Hardware buffer without double buffering works but then there is very + // annoying flickering of the OSD elements. + int flags = SDL_SWSURFACE; #else int flags = SDL_SWSURFACE; // Why did we use a SW surface again? #endif This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |