worker_respond is intended to be called when receiving a message from the main thread, generated using emscripten_call_worker. See the tests, tests/worker_api_worker.cpp and tests/worker_api_main.cpp for example.
- Alon On Thu, Oct 16, 2014 at 3:06 PM, Anthony Bobenrieth <[email protected]> wrote: > Hi, > > i am trying to do some "worker_respond" in a callback, inside a worker, > and it throws me Not in worker call exception related to this line of code > <https://github.com/kripken/emscripten/blob/master/src/library_browser.js#L1221> > : > > emscripten_worker_respond: function(data, size) { if (!inWorkerCall) throw > 'not > in worker call!'; > *But*, according to this stackoverflow answer > <http://stackoverflow.com/a/8906103/954853>, it only require to add > "this." to postMessage() to make it available outside of its call > function... and it seems to works fine when i directly edit the > library_browser.js. > > So, is it really wrong to use emscripten_respond in worker' callback this > way? > > thx! > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
