47 scenario in which extended bitmaps are used to store SVG data. (In the broadest |
47 scenario in which extended bitmaps are used to store SVG data. (In the broadest |
48 sense, you can consider SVG data to be a type of compression of bitmap data.) |
48 sense, you can consider SVG data to be a type of compression of bitmap data.) |
49 The following diagram shows how an extended bitmap that represents an icon |
49 The following diagram shows how an extended bitmap that represents an icon |
50 is ultimately displayed on the screen. </p> <fig id="GUID-690043B5-EF70-59BB-87D4-8B0B6EEA3F31"> |
50 is ultimately displayed on the screen. </p> <fig id="GUID-690043B5-EF70-59BB-87D4-8B0B6EEA3F31"> |
51 <title> Example extended bitmap scenario </title> |
51 <title> Example extended bitmap scenario </title> |
52 <image href="GUID-970A2948-5A72-5E92-84C0-86DDEE59A569_d0e264372_href.png" placement="inline"/> |
52 <image href="GUID-970A2948-5A72-5E92-84C0-86DDEE59A569_d0e262212_href.png" placement="inline"/> |
53 </fig> <p>This is how it works: </p> <ol id="GUID-2B3B99F0-BF43-5F1C-A86E-5E9605460D7E"> |
53 </fig> <p>This is how it works: </p> <ol id="GUID-2B3B99F0-BF43-5F1C-A86E-5E9605460D7E"> |
54 <li id="GUID-77F3E86D-7FC1-5682-90C0-EE83C8C39A22"><p>An engine or server |
54 <li id="GUID-77F3E86D-7FC1-5682-90C0-EE83C8C39A22"><p>An engine or server |
55 (the Theme Server in this example) creates an extended bitmap that stores |
55 (the Theme Server in this example) creates an extended bitmap that stores |
56 the icon's SVG data. </p> </li> |
56 the icon's SVG data. </p> </li> |
57 <li id="GUID-3F46695F-DAD7-58D8-822A-18EB89A0D119"><p>To the application, |
57 <li id="GUID-3F46695F-DAD7-58D8-822A-18EB89A0D119"><p>To the application, |
85 bitmap format in the render stage and a suitable extended bitmap rasterizer |
85 bitmap format in the render stage and a suitable extended bitmap rasterizer |
86 DLL, if support for drawing the extended bitmap through the BitGDI API is |
86 DLL, if support for drawing the extended bitmap through the BitGDI API is |
87 required.</p><fig id="GUID-3A965E47-106D-4EC3-BCFA-E2D40EDB2647"> |
87 required.</p><fig id="GUID-3A965E47-106D-4EC3-BCFA-E2D40EDB2647"> |
88 <title>The main participants in the extended bitmap framework, showing the |
88 <title>The main participants in the extended bitmap framework, showing the |
89 dependencies </title> |
89 dependencies </title> |
90 <image href="GUID-A67FFE7B-9573-543B-B3EA-0539278FE4AB_d0e264452_href.png" placement="inline"/> |
90 <image href="GUID-A67FFE7B-9573-543B-B3EA-0539278FE4AB_d0e262292_href.png" placement="inline"/> |
91 </fig><p>Although it is not possible to have more than one extended bitmap |
91 </fig><p>Although it is not possible to have more than one extended bitmap |
92 rasterizer DLL on a device, an extended bitmap rasterizer DLL can support |
92 rasterizer DLL on a device, an extended bitmap rasterizer DLL can support |
93 more than one type of proprietary data. Similarly, support for multiple data |
93 more than one type of proprietary data. Similarly, support for multiple data |
94 formats can be added to render stages.</p><p> The data format can be identified |
94 formats can be added to render stages.</p><p> The data format can be identified |
95 from the type UID. When you implement the extended bitmap feature in a device, |
95 from the type UID. When you implement the extended bitmap feature in a device, |