projects / qt4-x11.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1c99016) | 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)
committerRaspbian forward porter <root@raspbian.org>
Sun, 14 Jun 2015 16:38:43 +0000 (16:38 +0000)
commita56fc69f573819ce151a61130e3c07c241f50d54
tree13bcd9e06cc03e0fb817232a09c1277cad13f91ftree | snapshot
parent1c99016d53c6a1b50066a4e74f0cf6b2a326c2b5commit | 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.