summaryrefslogtreecommitdiffstats
path: root/examples/tutorials/gettingStarted/gsQt/part5
diff options
context:
space:
mode:
authorKevin Ottens <kevin.ottens.qnx@kdab.com>2012-05-07 15:51:55 (GMT)
committerQt by Nokia <qt-info@nokia.com>2012-05-10 10:53:01 (GMT)
commitc5e2c6ff19e816d45f0763d7339b7856080407f0 (patch)
treea52911edd3bad242e837e34afe3cb68169e154eb /examples/tutorials/gettingStarted/gsQt/part5
parent21d91ec14eea21f07bc58c171df000f87caf6c3d (diff)
downloadQt-c5e2c6ff19e816d45f0763d7339b7856080407f0.zip
Qt-c5e2c6ff19e816d45f0763d7339b7856080407f0.tar.gz
Qt-c5e2c6ff19e816d45f0763d7339b7856080407f0.tar.bz2
Always process window (de)activated events
QApplication::setActiveWindow() is fully able to deal with null pointers for the activated window. It is in fact necessary to call it even in case of a null pointer as it is the only way to get a ApplicationDeactivated event properly queued. Without this patch no ApplicationDeactivated event get delivered when the platform plugin informs the Qt event system of the corresponding user interaction. Note: This doesn't apply to qtbase which has the proper behavior, this bug is Qt4 specific. Change-Id: I1128d0233a8f85943cfe5fc3c298a43f66b6d4aa Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
Diffstat (limited to 'examples/tutorials/gettingStarted/gsQt/part5')
0 files changed, 0 insertions, 0 deletions