Searched refs:should_destroy (Results 1 - 9 of 9) sorted by relevance
/external/chromium_org/ppapi/thunk/ |
H A D | ppb_message_loop_api.h | 32 virtual int32_t PostQuit(PP_Bool should_destroy) = 0;
|
/external/chromium_org/ppapi/api/ |
H A D | ppb_message_loop.idl | 97 * loop (via PostQuit with should_destroy = PP_TRUE). In this case, any 102 * - You quit the message loop via PostQuit with should_destroy set to 106 * To do proper shutdown, call PostQuit with should_destroy = PP_TRUE. This 158 * as long as the thread is running or until you quit with should_destroy 232 * work after the message loop has exited as long as should_destroy was 256 * @param should_destroy Marks the message loop as being in a destroyed state 259 * If you quit a message loop without setting should_destroy, it will still 270 int32_t PostQuit([in] PP_Resource message_loop, PP_Bool should_destroy);
|
/external/chromium_org/ppapi/c/ |
H A D | ppb_message_loop.h | 115 * loop (via PostQuit with should_destroy = PP_TRUE). In this case, any 120 * - You quit the message loop via PostQuit with should_destroy set to 124 * To do proper shutdown, call PostQuit with should_destroy = PP_TRUE. This 173 * as long as the thread is running or until you quit with should_destroy 245 * work after the message loop has exited as long as should_destroy was 268 * @param should_destroy Marks the message loop as being in a destroyed state 271 * If you quit a message loop without setting should_destroy, it will still 282 int32_t (*PostQuit)(PP_Resource message_loop, PP_Bool should_destroy);
|
/external/chromium_org/ppapi/cpp/ |
H A D | message_loop.h | 102 /// loop (via PostQuit with should_destroy = PP_TRUE). In this case, any 107 /// - You quit the message loop via PostQuit with should_destroy set to 111 /// To do proper shutdown, call PostQuit with should_destroy = PP_TRUE. This 160 /// as long as the thread is running or until you quit with should_destroy 229 /// work after the message loop has exited as long as should_destroy was 250 /// @param should_destroy Marks the message loop as being in a destroyed 253 /// If you quit a message loop without setting should_destroy, it will still 263 int32_t PostQuit(bool should_destroy);
|
H A D | message_loop.cc | 80 int32_t MessageLoop::PostQuit(bool should_destroy) { argument 84 pp_resource(), PP_FromBool(should_destroy));
|
/external/chromium_org/ppapi/proxy/ |
H A D | ppb_message_loop_proxy.cc | 136 int32_t MessageLoopResource::PostQuit(PP_Bool should_destroy) { argument 140 if (PP_ToBool(should_destroy)) 254 int32_t PostQuit(PP_Resource message_loop, PP_Bool should_destroy) { argument 257 return enter.object()->PostQuit(should_destroy);
|
H A D | ppb_message_loop_proxy.h | 39 virtual int32_t PostQuit(PP_Bool should_destroy) OVERRIDE;
|
/external/chromium_org/mojo/examples/pepper_container_app/ |
H A D | mojo_ppapi_globals.cc | 68 virtual int32_t PostQuit(PP_Bool should_destroy) OVERRIDE {
|
/external/chromium_org/ppapi/native_client/src/untrusted/pnacl_irt_shim/ |
H A D | pnacl_shim.c | 1316 static int32_t Pnacl_M25_PPB_MessageLoop_PostQuit(PP_Resource message_loop, PP_Bool should_destroy) { argument 1318 return iface->PostQuit(message_loop, should_destroy); 4815 .PostQuit = (int32_t (*)(PP_Resource message_loop, PP_Bool should_destroy))&Pnacl_M25_PPB_MessageLoop_PostQuit
|
Completed in 185 milliseconds