Re: moveToWidget

Jorge Arellano Cid <[email protected]>
Newsgroups gmane.comp.web.dillo.devel
Message-ID <[email protected]>
On Sat, Jul 30, 2011 at 02:04:42PM +0000, corvid wrote:
> 
> If there's a link at the very top of the viewport and you move the
> mouse cursor up to the panel, the status output isn't cleared as you
> leave.

  Ah, yes.

  The attached patch fixes it.

  The interesting part is the amount of code that can be disabled
in  Layout::leaveNotify().  I've tested it for some time and have
found no regressions so far.

  Please test.


-- 
  Cheers
  Jorge.-

_______________________________________________
Dillo-dev mailing list
[email protected]
http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
crossing-events-part3.diff (text/x-diff, 1.1 KB)
diff -r 6234b0fda513 dw/layout.cc
--- a/dw/layout.cc	Sat Jul 30 13:21:37 2011 +0000
+++ b/dw/layout.cc	Sun Jul 31 14:57:38 2011 -0400
@@ -823,6 +823,7 @@ void Layout::enterNotify (View *view, in
  */
 void Layout::leaveNotify (View *view, ButtonState state)
 {
+#if 0
    Widget *lastWidget;
    EventCrossing event;
 
@@ -835,6 +836,9 @@ void Layout::leaveNotify (View *view, Bu
       event.currentWidget = widgetAtPoint;
       lastWidget->leaveNotify (&event);
    }
+#else
+   moveOutOfView (state);
+#endif
 }
 
 /*
diff -r 6234b0fda513 dw/textblock.cc
--- a/dw/textblock.cc	Sat Jul 30 13:21:37 2011 +0000
+++ b/dw/textblock.cc	Sun Jul 31 14:57:38 2011 -0400
@@ -592,7 +592,12 @@ void Textblock::enterNotifyImpl (core::E
 
 void Textblock::leaveNotifyImpl (core::EventCrossing *event)
 {
-   _MSG(" tb=%p, LEAVE NotifyImpl\n", this);
+   MSG(" tb=%p, LEAVE NotifyImpl: hoverLink=%d\n", this, hoverLink);
+
+   /* leaving the viewport can't be handled by motionNotifyImpl() */
+   if (hoverLink >= 0)
+      layout->emitLinkEnter (this, -1, -1, -1, -1);
+
    if (hoverTooltip) {
       hoverTooltip->onLeave();
       hoverTooltip = NULL;
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.