projects / qt4-x11.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 40486de) | 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)
committerFelix Geyer <fgeyer@debian.org>
Sun, 14 Jul 2019 10:19:27 +0000 (11:19 +0100)
commit20176c83cfbdd2c695939fd6da28a3fddcb58abd
tree9ebde336fa2940c0a483dad053786d35ea464d73tree | snapshot
parent40486de09d262d11d905ef43e08baad633c070cfcommit | 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.