summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_script_qscriptable.cpp
diff options
context:
space:
mode:
authorRichard Moe Gustavsen <richard.gustavsen@nokia.com>2010-04-13 12:57:00 (GMT)
committerRichard Moe Gustavsen <richard.gustavsen@nokia.com>2010-04-14 08:27:51 (GMT)
commitd3e91e4124b96869b8c4e2c8492b4d4cec913ebc (patch)
treeb0886255256015520e0ceb5ef09473cbc000aea2 /doc/src/snippets/code/src_script_qscriptable.cpp
parent7e1e691d0ae3c665ecb213ce7fd0e27d9838e5a9 (diff)
downloadQt-d3e91e4124b96869b8c4e2c8492b4d4cec913ebc.zip
Qt-d3e91e4124b96869b8c4e2c8492b4d4cec913ebc.tar.gz
Qt-d3e91e4124b96869b8c4e2c8492b4d4cec913ebc.tar.bz2
Cocoa: qwidget autotest fails on setToolTip
The reason turns out to be that we: 1. Half-way fake mouse events from QCursor::setPos 2. Don't fake mouse move upon mouse enter unless traking is on The test failed when mouse trackin was on, so that we ended up faking the same mouse move event twize (in QCursor::setPos and mouseEnter). We now do a different implementation for setPos on cocoa (so that native events will be generated), and always fake a mouse move event from mouse enter to make tooltips (and other event filters) work Reviewed-by: MortenS
Diffstat (limited to 'doc/src/snippets/code/src_script_qscriptable.cpp')
0 files changed, 0 insertions, 0 deletions