summaryrefslogtreecommitdiffstats
path: root/src/3rdparty
diff options
context:
space:
mode:
authorJanne Anttila <janne.anttila@digia.com>2009-11-04 13:21:37 (GMT)
committerJanne Anttila <janne.anttila@digia.com>2009-11-04 13:57:08 (GMT)
commitbe6357bfa96cdaffa5797fef99e95cac7121e5b3 (patch)
treef6bc6b53cc301bd749b98545ea887f376a655b6b /src/3rdparty
parent968eabf3ff6b686867d964f2a3437a228be0ea6b (diff)
downloadQt-be6357bfa96cdaffa5797fef99e95cac7121e5b3.zip
Qt-be6357bfa96cdaffa5797fef99e95cac7121e5b3.tar.gz
Qt-be6357bfa96cdaffa5797fef99e95cac7121e5b3.tar.bz2
Fixed modal dialog fading support in Symbian.
Switched to use S60 API instead of Symbian one, the rationale is given below as an copy/paste from S60 docs: "Cross-application fading support Symbian OS provides some support for fading, but this only covers fading within an application. The S60 UI can have more than one application on the screen at once (in fact, since the system parts of the Status pane are inside EikServer, it always has more than one application on the screen). The S60 UI introduced the fading and drawing system to manage the fading state for the whole system. Application and UI control code for S60 should not attempt to set fade for a popup window directly. Instead, the popup window should implement the MAknFadedComponent interface, and should use the TAknPopupFader support class to set the fade. The application UI base classes interact with the fading and drawing system by informing it when the foreground status of the application changes. They also use it to implement system wide fading." There is also task QTBUG-5393 to implement fading support in future without S60 dependency. Task-number: QTBUG-5181 Reviewed-by: Sami Merila
Diffstat (limited to 'src/3rdparty')
0 files changed, 0 insertions, 0 deletions