Archived:Custom window fading parameters do not work correctly (Known Issue)
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.
No known solution.