Archived:DSA API not supported by compatibility mode in scalable UI platforms (Known Issue)
hamishwillee
(Talk | contribs) m (moved DSA API not supported by compatibility mode in scalable UI platforms (Known Issue) to Archived:DSA API not supported by compatibility mode in scalable UI platforms (Known Issue)) |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Archived|timestamp=20120403201117|user=[[User:Lpvalente|Lpvalente]]}} |
| − | + | [[Category:Known Issue]][[Category:Symbian C++]][[Category:S60 2nd Edition (initial release)]] | |
| − | + | ||
| − | + | ||
| − | | | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | |- | + | {{ArticleMetaData <!-- v1.2 --> |
| − | | | + | |sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> |
| − | ===== | + | |installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) --> |
| − | | | + | |devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') --> |
| + | |sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) --> | ||
| + | |platform= S60 2nd Edition, Feature Pack 3 and onwards | ||
| + | |devicecompatability= <!-- Compatible devices (e.g.: All* (must have GPS) ) --> | ||
| + | |dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 --> | ||
| + | |signing= <!-- Empty or one of Self-Signed, DevCert, Manufacturer --> | ||
| + | |capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. --> | ||
| + | |keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase --> | ||
| + | |language= <!-- Language category code for non-English topics - e.g. Lang-Chinese --> | ||
| + | |translated-by= <!-- [[User:XXXX]] --> | ||
| + | |translated-from-title= <!-- Title only --> | ||
| + | |translated-from-id= <!-- Id of translated revision --> | ||
| + | |review-by= <!-- After re-review: [[User:username]] --> | ||
| + | |review-timestamp= <!-- After re-review: YYYYMMDD --> | ||
| + | |update-by= <!-- After significant update: [[User:username]]--> | ||
| + | |update-timestamp= <!-- After significant update: YYYYMMDD --> | ||
| + | |creationdate= May 4, 2005, updated May 24, 2005 | ||
| + | |author= [[User:Technical writer 1]] | ||
| + | <!-- The following are not in current metadata --> | ||
| + | |subcategory= | ||
| + | |id= KIS000247 | ||
| + | }} | ||
| − | + | ==Overview== | |
| − | + | {{Abstract|The DSA API is not supported by the compatibility mode in scalable UI platforms.}} | |
| − | + | ||
| − | | | + | |
| − | + | ==Description== | |
| − | + | The Direct Screen Access (DSA) API (RDirectScreenAccess and CDirectScreenAccess classes, defined in w32std.h) is meant for very low-level operations with display hardware. In platforms supporting the scalable UI (S60 2nd Edition FP3 and onwards) DSA API is not supported by the compatibility mode.<br>For this and other breaks between different platforms, refer to the document S60 Platform: Source And Binary Compatibility. | |
| − | + | ||
| − | + | ||
| − | + | ==How to reproduce== | |
| − | + | Applications working correctly in earlier S60 devices using the Direct Screen Access API may behave unexpectedly in Feature Pack 3 devices (with varying display characteristics), because, for example, the N90 has more resolution and a different color depth (18-bit colors) than previous S60 devices. Applications that use this API to access display buffer (memory) directly, may encounter different problems depending on how the applications have been implemented. Some applications render their screen only to 1/4th portion of the screen, whereas some may fill the screen with garbage, have incorrect colors, or may exit when they notice that the display attributes are not what they assume. | |
| − | + | ||
| − | + | ||
| − | + | ==Solution== | |
| − | + | Possible changes in resolutions between S60 devices must be taken into account when developing applications. You can use CFbsScreenDevice::SizeInPixels() to get the current display size. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 03:44, 19 June 2012
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
The article is believed to be still valid for the original topic scope.
The article is believed to be still valid for the original topic scope.
Article Metadata
Compatibility
Platform(s): S60 2nd Edition, Feature Pack 3 and onwards
Article
Created: User:Technical writer 1
(May 4, 2005, updated May 24, 2005)
Last edited: hamishwillee
(19 Jun 2012)
Contents |
Overview
The DSA API is not supported by the compatibility mode in scalable UI platforms.
Description
The Direct Screen Access (DSA) API (RDirectScreenAccess and CDirectScreenAccess classes, defined in w32std.h) is meant for very low-level operations with display hardware. In platforms supporting the scalable UI (S60 2nd Edition FP3 and onwards) DSA API is not supported by the compatibility mode.
For this and other breaks between different platforms, refer to the document S60 Platform: Source And Binary Compatibility.
How to reproduce
Applications working correctly in earlier S60 devices using the Direct Screen Access API may behave unexpectedly in Feature Pack 3 devices (with varying display characteristics), because, for example, the N90 has more resolution and a different color depth (18-bit colors) than previous S60 devices. Applications that use this API to access display buffer (memory) directly, may encounter different problems depending on how the applications have been implemented. Some applications render their screen only to 1/4th portion of the screen, whereas some may fill the screen with garbage, have incorrect colors, or may exit when they notice that the display attributes are not what they assume.
Solution
Possible changes in resolutions between S60 devices must be taken into account when developing applications. You can use CFbsScreenDevice::SizeInPixels() to get the current display size.
