From 8ddcc01712b0971c6a5714fa59ff3c7c6ad4c51f Mon Sep 17 00:00:00 2001 From: Andrea Diamantini Date: Fri, 23 Oct 2009 12:12:51 +0200 Subject: What's overkilling? checking EVERYTIME mouse move events to just fix some stupid cases? revert a good implementation just to bug fixing the 0.1% of the cases? Don't know! This implementation seems working to fix the flickering links But, these are really the UI problems I'd like to get rid... --- src/webview.cpp | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'src/webview.cpp') diff --git a/src/webview.cpp b/src/webview.cpp index e65aea9e..8380d064 100644 --- a/src/webview.cpp +++ b/src/webview.cpp @@ -451,6 +451,16 @@ void WebView::mousePressEvent(QMouseEvent *event) void WebView::mouseMoveEvent(QMouseEvent *event) { + QPoint p = event->pos(); + QSize s = size(); + int x = s.width() / 2; + int y = s.height() - 30; // quite reasonable value, without performing requests, cause of speed + + if(p.x() <= x && p.y() >= y ) + Application::instance()->mainWindow()->setFlickeringZone(true); + else + Application::instance()->mainWindow()->setFlickeringZone(false); + if( url().protocol() != "rekonq" ) { QWebView::mouseMoveEvent(event); -- cgit v1.2.1