ah ok. It would be good to know the failing order... so other people can work around it... or maybe we can fix it.
cu, On Mon, May 11, 2009 at 11:25 AM, Adam Li <ada...@hyervision.com> wrote: > Hi Rene, > > Thanks for your reply. The little Atom board (it is a custom-built board) > is running standard Windows XP. > > pygame.display.list_modes() returns: > > [(1280, 1024), (1280, 1024), (1280, 960), (1280, 768), (1280, 720), (1152, > 864), (1024, 768), (960, 540), (800, 600), (800, 480), (720, 480), (640, > 480)] > > The LCD is 1280x1024. I have tried to call set_mode with (0, 0), (1280, > 1024), and (640, 480) and all getting the same problem. > > On a plus note, after a lot of tried this afternoon, I was able to get it > to work by shuffling the order of the initialization code between pygame and > other modules I am loading. So maybe the problem is with the conflicting > access to resources, or something. > > I am using pygame, PIL, and a webcam module called VideoCapture. Hope it > helps. > > Thanks, > > Adam > > > > > René Dudfield wrote: > >> hi, >> >> definitely sounds like a bug... but most likely in the X. >> >> Have you used list_modes first? >> http://www.pygame.org/docs/ref/display.html#pygame.display.list_modes >> >> What does your little computer say are available? >> >> cu, >> >> >> >> On Mon, May 11, 2009 at 8:47 AM, Adam Li <ada...@hyervision.com <mailto: >> ada...@hyervision.com>> wrote: >> >> Hi there, >> >> Just wrote small code to test different screen mode. It works well >> on my desktop, but when I moved it to an Atom-based computer, >> there is a problem. >> >> The code appears to hang when I set_mode with FULLSCREEN. Again, >> the same code works without problem on my desktop, but not on this >> small Atom-based computer. Other modes works fine on both >> computers as well, as long as I don't set the FULLSCREEN flag. >> >> The display adapter is "Intel US15 Embedded Graphics Chipset >> Function 0". >> >> Any idea? Could it be a bug? >> >> Thanks, >> >> Adam >> >> >> >> >> >
