On Tue, Oct 23, 2012 at 9:47 PM, Blaine <[email protected]> wrote: > Thanks. Getting close! I figured out how to actually talk with the main > thread, but the framebuffer refuses to update. I made a new issue. Any > ideas? > http://code.google.com/p/los-cocos/issues/detail?id=187 > > Maybe I'm doing inter-process communication incorrectly, but at least I am > succeeding in getting messages to get passed to the right instance. Now > it's a matter of getting pyglet/cocos to update the framebuffer. At least I > think that's the case. > > > I'm unclear about your design. You want a browser (or other app) to communicate trough html with a cocos + flask app ?
And your problem is the communication between cocos and flask ? For the last, lets check some basics: The gui thread (the one where the pyglet window is created) should be the main thread, ie the only one that exists when the process starts. This condition is fulfilled in your app ? Be sure the communication between the flask thread and the main thread is non blocking. The flask operation (facing the client) is non blocking ? I know nothing about flask. How many messages per seconds are pumped to cocos ? Anything special about self.next_scene ? Finally, if you can present a small, runnable sample it would help a lot. -- 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.
