1<html>
2
3<head>
4<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
5<LINK rel="stylesheet" type="text/css" href="../CSS/revolution.css">
6
7<title>MPWaitPseudoVBlank</title>
8</head>
9
10<body>
11<h1>MPWaitPseudoVBlank</h1>
12
13<h2>Syntax</h2>
14<p>
15<dl>
16  <dd><pre><code>#include &lt;revolution/mp.h&gt;</code></pre>
17  </dd>
18  <dd><pre><code>BOOL MPWaitPseudoVBlank ( void );</code></pre>
19  </dd>
20</dl>
21</p>
22
23<h2>Arguments</h2>
24<p>
25None.
26</p>
27
28<h2>Return Values</h2>
29
30<P>Returns <CODE>TRUE</CODE> if waiting on a pseudo V-Blank. Returns <CODE>FALSE</CODE> if not waiting on a pseudo V-Blank, such as when MP communications are not running.</P>
31
32<h2>Description</h2>
33
34<p>Puts the current thread to sleep until the time for the pseudo V-Blank arrives. It will be awakened when the time for the pseudo V-Blankk arrives or when the MP library has been closed.</p>
35
36<p>A pseudo V-Blank automatically synchronizes connected child devices. It occurs on a 60-Hz cycle (approximately) and is unrelated to the screen update cycle for the Wii console. Child devices connected to the Wii console continuously and automatically synchronize their own V-Blank cycles to the pseudo V-Blank timing. Frame-synchronized MP communications will begin a fixed period of time after a pseudo V-Blank occurs. By setting the send data with the same timing as the pseudo V-Blank timing, it is possible to stabilize and reduce the latency for data arriving at child devices.</p>
37
38<h2>See Also</h2>
39<p>
40None.
41</p>
42
43<h2>Revision History</h2>
44
45<p>2008/06/05 Initial version.</p>
46
47<hr><p>CONFIDENTIAL</p></body>
48</html>