×
Namespaces

Variants
Actions

Archived:Custom window fading parameters do not work correctly (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search

Archived.pngArchived: 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}}.

Article Metadata
Compatibility
Platform(s): S60 3rd Edition,
S60 3rd Edition, FP1
S60 3rd Edition FP1
S60 3rd Edition (initial release)
Article
Created: User:Technical writer 1 (29 Aug 2007)
Last edited: hamishwillee (18 Jun 2012)

Description

When using one of the following methods to set a custom fade map for a window, the results vary depending on the device and the current screen orientation:

void RWsSession::SetDefaultFadingParameters( TUInt8 aBlackMap, TUint8 aWhiteMap );
void RWindowTreeNode::SetFaded( TBool aFaded, TFadeControl aIncludeChildren, TUInt8 aBlackMap, TUint8 aWhiteMap );

For some devices, the custom fading parameters are ignored, while for others (e.g. Nokia N95), the fading works in portrait mode but has no effect in landscape mode. In landscape mode the system default fade map is always applied. This is true whether that application is started in portrait mode and switched to landscape mode or started in landscape mode.

Additionally, if UI controls are redrawn in the portrait mode while they are faded (with custom parameters), drawing is done using the system default fade map instead of the custom map.

Solution

No known solution.

This page was last modified on 18 June 2012, at 12:23.
57 page views in the last 30 days.
×