projects / qt4-x11.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 58cc39d) | patch
Fix logic for figuring out what ConfigureNotify positions can be trusted
authorOwen W. Taylor <otaylor@fishsoup.net>
Mon, 17 Oct 2011 21:27:43 +0000 (17:27 -0400)
committerLisandro Damián Nicanor Pérez Meyer <lisandro@debian.org>
Tue, 15 May 2018 16:24:10 +0000 (17:24 +0100)
commit0cc1562e680b1fc2ed79cbf39a4c348d5a8577a1
tree54670174bce8d6fa406362c1e359d190a40b60aftree | snapshot
parent58cc39d2e131911041d35b1bddc272f0c6e3d1b8commit | diff
Fix logic for figuring out what ConfigureNotify positions can be trusted

When reading ahead in the queue for ConfigureNotify events, it's necessary
to look for intermediate ReparentNotify events as well, since they will
determine whether the position in the event can be trusted or not.

Bug: https://bugreports.qt.nokia.com/browse/QTBUG-21900

Gbp-Pq: Name QTBUG-21900_Buttons_in_Qt_applications_not_clickable_when_run_under_gnome-shell.patch
src/gui/kernel/qapplication_x11.cpp diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.