Symbian3/PDK/Source/GUID-D76C7759-739D-5C98-B718-7297687FE630.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e
--- a/Symbian3/PDK/Source/GUID-D76C7759-739D-5C98-B718-7297687FE630.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-D76C7759-739D-5C98-B718-7297687FE630.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -49,7 +49,7 @@
 The following diagram shows how an extended bitmap that represents an icon
 is ultimately displayed on the screen. </p> <fig id="GUID-690043B5-EF70-59BB-87D4-8B0B6EEA3F31">
 <title>              Example extended bitmap scenario            </title>
-<image href="GUID-970A2948-5A72-5E92-84C0-86DDEE59A569_d0e258363_href.png" placement="inline"/>
+<image href="GUID-970A2948-5A72-5E92-84C0-86DDEE59A569_d0e264372_href.png" placement="inline"/>
 </fig> <p>This is how it works: </p> <ol id="GUID-2B3B99F0-BF43-5F1C-A86E-5E9605460D7E">
 <li id="GUID-77F3E86D-7FC1-5682-90C0-EE83C8C39A22"><p>An engine or server
 (the Theme Server in this example) creates an extended bitmap that stores
@@ -87,7 +87,7 @@
 required.</p><fig id="GUID-3A965E47-106D-4EC3-BCFA-E2D40EDB2647">
 <title>The main participants in the extended bitmap framework, showing the
 dependencies </title>
-<image href="GUID-A67FFE7B-9573-543B-B3EA-0539278FE4AB_d0e258443_href.png" placement="inline"/>
+<image href="GUID-A67FFE7B-9573-543B-B3EA-0539278FE4AB_d0e264452_href.png" placement="inline"/>
 </fig><p>Although it is not possible to have more than one extended bitmap
 rasterizer DLL on a device, an extended bitmap rasterizer DLL can support
 more  than one type of proprietary data. Similarly, support for multiple data