diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-B1CB6374-2C2B-5D6C-9A7C-6E49D8F235B8.dita
--- a/Symbian3/SDK/Source/GUID-B1CB6374-2C2B-5D6C-9A7C-6E49D8F235B8.dita Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-B1CB6374-2C2B-5D6C-9A7C-6E49D8F235B8.dita Tue Jul 20 12:00:49 2010 +0100
@@ -58,7 +58,7 @@
enabling display change event notifications (EEventDisplayChanged).
The following diagram shows the class hierarchy.
Display control class diagram
-
+
Once you have obtained
the MDisplayControl interface, you can call GetResolutions() on
it. For example:
// Get available resolutions
@@ -167,7 +167,7 @@
so that the virtual keyboard can be drawn within the full UI area but outside
of the application's extent.
Display mapping class diagram
-
+
The MDisplayMapping interface is very
flexible. UIDs are used to signify the application UI coordinate space, the
full UI space, the composition/display coordinate space (which may be a different
@@ -182,7 +182,7 @@
rectangle represents the display area and the inner one represents the application
space (screen mode).
Display area and application extent
-
+
The display resolution is 1280 x 720, the application size is 176
x 208 and a virtual resolution of 426 x 240 has been introduced, which gives
a scaling factor of three in each direction. All pixels are approximately