projects / qt4-x11.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 13b8451) | 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)
committerPeter Michael Green <plugwash@raspbian.org>
Sun, 14 Apr 2019 10:25:37 +0000 (11:25 +0100)
commit37630b2f1cf2279de2217d10e43a798206a65a8c
treee807c77bf09afe0f371eff1eb92b31c70564d959tree | snapshot
parent13b84514cf891b1a72bf7c55add0316c32715452commit | 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.