Symbian3/PDK/Source/GUID-F32E2F00-B68F-59B2-AABA-181E16354C86.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e
--- a/Symbian3/PDK/Source/GUID-F32E2F00-B68F-59B2-AABA-181E16354C86.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-F32E2F00-B68F-59B2-AABA-181E16354C86.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -35,7 +35,7 @@
 on to the next control in the hierarchy. </p><p>The sequence diagram below
 illustrates the Object Provider process for supplying an interface pointer
 from the run-time hierarchy. </p><fig id="GUID-91496FA9-60F6-5DDA-899B-7E54A8A7E4CB">
-<image href="GUID-DF3ECD47-4A5B-5836-B5CA-ACCEE98412D4_d0e74379_href.png" placement="inline"/>
+<image href="GUID-DF3ECD47-4A5B-5836-B5CA-ACCEE98412D4_d0e78592_href.png" placement="inline"/>
 </fig><p>Object1 wishes to call a function on <codeph>MInterface</codeph>.
 It calls <codeph>MopGetObject()</codeph> on the nearest control in the run-time
 hierarchy. The Object Provider Framework identifies the Uid for <codeph>Minterface</codeph> and