On Tue, Oct 23, 2012 at 8:00 PM, Blaine <[email protected]> wrote: > Hi guys. > > I'd like to make a simple web interface to controlling a cocos app. I'm > having a hard time figuring out how to handle events and threading. I'm > using the director interface and it's working perfectly on its own! > > Let's say that at a basic level I'd like to be able to "emit a signal" > that can be captured by my app (next scene, previous scene, etc.). Is there > a good way to handle this without hacking the director interface? I've > already tried sharing instances between threads (for the purpose of calling > methods directly) but this doesn't work. Would I be able to register events > and generate them from another thread that would be captured by the cocos > app? Ideally I'd like to use Flask for the API but since it has its won > blocking .run() call I'd need it to be in its own thread. > > What do you guys think? Thanks! > Blaine > -- >
Have a look to this thread: http://groups.google.com/group/cocos-discuss/browse_thread/thread/706c1bbbbf04f8ce/d87345d509000e35?hl=en_US&lnk=gst&q=threading#d87345d509000e35 It helps ? -- 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.
