Symbian3/PDK/Source/GUID-C21BB0E4-7AF7-58E5-AAD6-8CE67399460C.dita
changeset 14 578be2adaf3e
parent 12 80ef3a206772
--- a/Symbian3/PDK/Source/GUID-C21BB0E4-7AF7-58E5-AAD6-8CE67399460C.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-C21BB0E4-7AF7-58E5-AAD6-8CE67399460C.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -28,7 +28,7 @@
 More information about running the example is given in the build section
 of this document. </p> <p><b>Design</b> </p> <p>The following block
 diagram describes the example in more detail. </p> <fig id="GUID-27A0C389-EDDD-5E17-82EE-2727F21803AF">
-<image href="GUID-CD7F507C-CDD5-5612-BA1B-72641D28FA4A_d0e361654_href.png" placement="inline"/>
+<image href="GUID-CD7F507C-CDD5-5612-BA1B-72641D28FA4A_d0e359491_href.png" placement="inline"/>
 </fig><p><filepath>CCollector.exe</filepath> is the Collector process.
 The user starts the Collector and creates an active scheduler and
 two global message queues. It also starts the Inverter process called <filepath>Inverter.exe</filepath>. The Collector creates one active object
@@ -48,7 +48,7 @@
 the message queue, receives the received words and displays  them
 in its console. It uses the <xref href="GUID-22E24B08-175B-3446-9D48-9AC4B1663E35.dita"><apiname>NotifyDataAvailable(TRequestStatus&amp;)</apiname></xref> API to monitor the queue for the next set of data. </p><p>The Class
 diagram of the example is shown below </p><fig id="GUID-E93EF1D6-1B9D-4C76-80B0-1FF660B5C75A">
-<image href="GUID-3560E862-CB68-584F-B9B6-FCD9F0D202DC_d0e361702_href.png" placement="inline"/>
+<image href="GUID-3560E862-CB68-584F-B9B6-FCD9F0D202DC_d0e359539_href.png" placement="inline"/>
 </fig> </section>
 <section id="GUID-86B04D06-7046-49BD-AE1A-57D5E406F864"><title>Class
 summary</title><ul>