On Fri, Aug 5, 2011 at 2:07 AM, claudio canepa <[email protected]> wrote:
> > > The only thing that precludes me to chose pure pygame is that, at the times > of pygame 1.7, some modules would not work without instantiating a pygame > window. But I don't remember which modules, and don't know potential changes > to the current pygame version. > > Done some other tests with pure pygame + cocos: streaming music from filesystem works (pygame.mixer.music) But reading the pygame docs: 1. I found this under pygame.mixer.init: """Some platforms require the pygame.mixer module to be initialized after the display modules have initialized.""" 2. the pygame events that can be generated on request by the sound subsystem don't allow to set a callback, they will go to the pygame event queue. And pygame.event complains 'video system not initialized' when doing pygame.event.get(). Thus, with pure pygame + cocos to know 'end of sound' or other sound events the only way is pulling state from the subsystem. So, I would discard pure pygame and go for the SDL backend. Another interesting thing that I found was a comment in the online docs: """ For this error : 'there is no soundcard' Call pygame.mixer.init two times : pygame.mixer.init() pygame.mixer.init() """ -- claudio -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cocos-discuss?hl=en.
