Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(521)

Side by Side Diff: native_client_sdk/doc_generated/pepper_beta/c/struct_p_p_b___message_loop__1__0.html

Issue 2875303003: Add migration to WebAssembly information to PNaCl / NaCl docs. (Closed)
Patch Set: fix Created 3 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 {{+bindTo:partials.standard_nacl_api}} 1 {{+bindTo:partials.standard_nacl_api}}
2 <h1>PPB_MessageLoop Struct Reference</h1> 2 <h1>PPB_MessageLoop Struct Reference</h1>
3 <div id="doxygen-ref"> 3 <div id="doxygen-ref">
4 {{- dummy div to appease doxygen -}} 4 {{- dummy div to appease doxygen -}}
5 <div> 5 <div>
6 <!-- Generated by Doxygen 1.7.6.1 --> 6 <!-- Generated by Doxygen 1.7.6.1 -->
7 7
8 8
9 </div> 9 </div>
10 <!--header--> 10 <!--header-->
(...skipping 194 matching lines...) Expand 10 before | Expand all | Expand 10 after
205 <table class="memname"> 205 <table class="memname">
206 <tr> 206 <tr>
207 <td class="memname">int32_t(* <a class="el" href="struct_p_p_b___message_loop__1 __0.html#a2262dd5022845450f77b3601578cc22d">PPB_MessageLoop::Run</a>)(<a class=" el" href="group___typedefs.html#gafdc3895ee80f4750d0d95ae1b677e9b7">PP_Resource< /a> message_loop)</td> 207 <td class="memname">int32_t(* <a class="el" href="struct_p_p_b___message_loop__1 __0.html#a2262dd5022845450f77b3601578cc22d">PPB_MessageLoop::Run</a>)(<a class=" el" href="group___typedefs.html#gafdc3895ee80f4750d0d95ae1b677e9b7">PP_Resource< /a> message_loop)</td>
208 </tr> 208 </tr>
209 </table> 209 </table>
210 </div> 210 </div>
211 <div class="memdoc"> 211 <div class="memdoc">
212 <p>Runs the thread message loop. </p> 212 <p>Runs the thread message loop. </p>
213 <p>Running the message loop is required for you to get issued completion callbac ks on the thread.</p> 213 <p>Running the message loop is required for you to get issued completion callbac ks on the thread.</p>
214 <p>The message loop identified by the argument must have been previously success fully attached to the current thread.</p> 214 <p>The message loop identified by the argument must have been previously success fully attached to the current thread.</p>
215 <p>You may not run nested run loops. Since the main thread has an implicit messa ge loop that the system runs, you may not call Run on the main thread.</p> 215 <p>You may not run nested message loops. Since the main thread has an implicit m essage loop that the system runs, you may not call Run on the main thread.</p>
216 <dl class="return"><dt><b>Returns:</b></dt><dd><ul> 216 <dl class="return"><dt><b>Returns:</b></dt><dd><ul>
217 <li>PP_OK: The message loop was successfully run. Note that on success, the mess age loop will only exit when you call <a class="el" href="struct_p_p_b___message _loop__1__0.html#adbbdc03661c9ac41df82fffcc566603d" title="Posts a quit message to the given message loop's work queue.">PostQuit()</a>.</li> 217 <li>PP_OK: The message loop was successfully run. Note that on success, the mess age loop will only exit when you call <a class="el" href="struct_p_p_b___message _loop__1__0.html#adbbdc03661c9ac41df82fffcc566603d" title="Posts a quit message to the given message loop's work queue.">PostQuit()</a>.</li>
218 <li>PP_ERROR_BADRESOURCE: The given message loop resource is invalid.</li> 218 <li>PP_ERROR_BADRESOURCE: The given message loop resource is invalid.</li>
219 <li>PP_ERROR_WRONG_THREAD: You are attempting to run a message loop that has not been successfully attached to the current thread. Call <a class="el" href="stru ct_p_p_b___message_loop__1__0.html#ad7e1c1fb0baf6a0446ffb241a6b226b9" title="Set s the given message loop resource as being the associated message loop for the c urrently running t...">AttachToCurrentThread()</a>.</li> 219 <li>PP_ERROR_WRONG_THREAD: You are attempting to run a message loop that has not been successfully attached to the current thread. Call <a class="el" href="stru ct_p_p_b___message_loop__1__0.html#ad7e1c1fb0baf6a0446ffb241a6b226b9" title="Set s the given message loop resource as being the associated message loop for the c urrently running t...">AttachToCurrentThread()</a>.</li>
220 <li>PP_ERROR_INPROGRESS: You are attempting to call Run in a nested fashion (Run is already on the stack). This will occur if you attempt to call run on the mai n thread's message loop (see above). </li> 220 <li>PP_ERROR_INPROGRESS: You are attempting to call Run in a nested fashion (Run is already on the stack). This will occur if you attempt to call run on the mai n thread's message loop (see above). </li>
221 </ul> 221 </ul>
222 </dd></dl> 222 </dd></dl>
223 </div> 223 </div>
224 </div> 224 </div>
225 <hr />The documentation for this struct was generated from the following file:<u l> 225 <hr />The documentation for this struct was generated from the following file:<u l>
226 <li><a class="el" href="ppb__message__loop_8h.html">ppb_message_loop.h</a></li> 226 <li><a class="el" href="ppb__message__loop_8h.html">ppb_message_loop.h</a></li>
227 </ul> 227 </ul>
228 </div><!-- contents --> 228 </div><!-- contents -->
229 </div> 229 </div>
230 {{/partials.standard_nacl_api}} 230 {{/partials.standard_nacl_api}}
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698