summaryrefslogtreecommitdiffstats
path: root/src/plugins/platforms/xcb/qxcbbackingstore.cpp
diff options
context:
space:
mode:
authorTimur Pocheptsov <timur.pocheptsov@theqtcompany.com>2016-03-22 18:02:26 +0100
committerTimur Pocheptsov <timur.pocheptsov@theqtcompany.com>2016-03-30 10:44:08 +0000
commit3439705c2d4e5a1a2817e91d1ce4553dde81d2fe (patch)
treeb184c1bcc6395f6256a99da37d60355389748c12 /src/plugins/platforms/xcb/qxcbbackingstore.cpp
parent91f8c9cc70bbfb752811cd29945fb37ff863d524 (diff)
Cocoa integration - hitTest for Qt::WindowTransparentForInput
In case Qt::WindowTransparentForInput is set on a window, we usually call [super someRelatedMethod] on a corresponding QNSView, for example, [super mouseDown:theEvent]. Unfortunately, Cocoa will continue to report the subsequent mouse dragging events to the first view where mouse down occurred, despite of us passing mouse down to the next reponder. Dragging events we'll also 'propagate' by calling super's method, but it's not working properly, since the current view below probably did not have that first mouse down event thus it does not have m_buttons set correctly. And even worse with the closing mouseUp event. So, let's use -hitTest: returning nil on such a 'transparent' view so that it's ignored by mouse events. Task-number: QTBUG-40583 Change-Id: I5e0fef3e246a29332df758a692300d478b862069 Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>
Diffstat (limited to 'src/plugins/platforms/xcb/qxcbbackingstore.cpp')
0 files changed, 0 insertions, 0 deletions