36 (which is not drawn to scale). The screen mode is still used in the same way |
36 (which is not drawn to scale). The screen mode is still used in the same way |
37 in the <xref href="GUID-F64E6551-670E-5E12-8103-DE504D3EC94F.dita">non-ScreenPlay |
37 in the <xref href="GUID-F64E6551-670E-5E12-8103-DE504D3EC94F.dita">non-ScreenPlay |
38 variant</xref>. </p> <fig id="GUID-FF86B974-1B1E-5EE1-A88A-9CD11B213A9B"> |
38 variant</xref>. </p> <fig id="GUID-FF86B974-1B1E-5EE1-A88A-9CD11B213A9B"> |
39 <title>The screen mode enables old applications to run on new |
39 <title>The screen mode enables old applications to run on new |
40 phones with higher resolutions </title> |
40 phones with higher resolutions </title> |
41 <image href="GUID-AFC49653-78E6-5639-911C-E02AEB08AFFC_d0e191929_href.png" placement="inline"/> |
41 <image href="GUID-AFC49653-78E6-5639-911C-E02AEB08AFFC_d0e185333_href.png" placement="inline"/> |
42 </fig> <p>There are several similar use cases, such as swapping between portrait |
42 </fig> <p>There are several similar use cases, such as swapping between portrait |
43 and landscape orientations and flip phones that have a flap that, when closed, |
43 and landscape orientations and flip phones that have a flap that, when closed, |
44 partially obscures the main screen. The Window Server uses the screen mode |
44 partially obscures the main screen. The Window Server uses the screen mode |
45 parameters to display applications differently depending on whether the phone |
45 parameters to display applications differently depending on whether the phone |
46 is in portrait or landscape orientation and whether the flap is open or closed. |
46 is in portrait or landscape orientation and whether the flap is open or closed. |
68 scaling</b> means that both pixel axes are scaled by the same arbitrary factor. </p> <p>The |
68 scaling</b> means that both pixel axes are scaled by the same arbitrary factor. </p> <p>The |
69 following diagram illustrates how the full UI area is mapped to fill the display/composition |
69 following diagram illustrates how the full UI area is mapped to fill the display/composition |
70 area. The application's area (which corresponds to the screen mode) is referred |
70 area. The application's area (which corresponds to the screen mode) is referred |
71 to as the <b>application extent</b> in ScreenPlay. </p> <fig id="GUID-724DB4EE-1F45-58D9-889C-B42ECEE7208D"> |
71 to as the <b>application extent</b> in ScreenPlay. </p> <fig id="GUID-724DB4EE-1F45-58D9-889C-B42ECEE7208D"> |
72 <title>Coordinate spaces in ScreenPlay </title> |
72 <title>Coordinate spaces in ScreenPlay </title> |
73 <image href="GUID-A719FDFA-903B-5340-AA47-9E5B22DBB253_d0e191975_href.png" placement="inline"/> |
73 <image href="GUID-A719FDFA-903B-5340-AA47-9E5B22DBB253_d0e185379_href.png" placement="inline"/> |
74 </fig> <p>ScreenPlay handles application sizing and positioning in a fundamentally |
74 </fig> <p>ScreenPlay handles application sizing and positioning in a fundamentally |
75 different way from the non-ScreenPlay variant. Using a fixed offset to position |
75 different way from the non-ScreenPlay variant. Using a fixed offset to position |
76 the application within the screen is inadequate when connecting to an external |
76 the application within the screen is inadequate when connecting to an external |
77 HDMI display, for example, when the resolution may not be known until runtime. |
77 HDMI display, for example, when the resolution may not be known until runtime. |
78 For example, the offset designed for a QVGA display does not position the |
78 For example, the offset designed for a QVGA display does not position the |
79 application correctly in a higher resolution display, as shown in the following |
79 application correctly in a higher resolution display, as shown in the following |
80 diagram, where the red cross indicates the offset for a QVGA display. </p> <fig id="GUID-A2816D08-B61F-5605-B6AF-A9D186F6BED5"> |
80 diagram, where the red cross indicates the offset for a QVGA display. </p> <fig id="GUID-A2816D08-B61F-5605-B6AF-A9D186F6BED5"> |
81 <title>A fixed offset and several display resolutions (not drawn |
81 <title>A fixed offset and several display resolutions (not drawn |
82 to scale) </title> |
82 to scale) </title> |
83 <image href="GUID-B2E63B13-7B72-5CBF-ACD0-1F2D2E1EEF19_d0e191986_href.png" placement="inline"/> |
83 <image href="GUID-B2E63B13-7B72-5CBF-ACD0-1F2D2E1EEF19_d0e185390_href.png" placement="inline"/> |
84 </fig> <p>In ScreenPlay there is no scaling of the application extent relative |
84 </fig> <p>In ScreenPlay there is no scaling of the application extent relative |
85 to the full UI area—there is always a 1:1 pixel correspondence between them. |
85 to the full UI area—there is always a 1:1 pixel correspondence between them. |
86 In addition, although supported, the screen mode offset is not necessarily |
86 In addition, although supported, the screen mode offset is not necessarily |
87 used. Instead, the render stage chain selects an appropriate virtual resolution |
87 used. Instead, the render stage chain selects an appropriate virtual resolution |
88 and handles the positioning—for example, centering it and using a best fit |
88 and handles the positioning—for example, centering it and using a best fit |