aboutsummaryrefslogtreecommitdiff
path: root/dw/layout.cc
diff options
context:
space:
mode:
authorcorvid <corvid@lavabit.com>2011-02-24 04:56:13 +0000
committercorvid <corvid@lavabit.com>2011-02-24 04:56:13 +0000
commite90273b90ea846855dfeb5fd675104d26114701e (patch)
tree7a415a6e5ddb93b214c21bbd3473f473123b58ce /dw/layout.cc
parentbc476c13039158dea4e5370987f5f5adbff4f02d (diff)
add some band-aids again for now for this whole events-during-deletion problem
Conceptually, what feels like it 'should' happen when the form widgets are deleted and MOVEs and LEAVEs and whatnot are flying around is for the viewport not to do anything with events. But it would want to accept FOCUS, and no doubt there are other cases to make it not so simple.
Diffstat (limited to 'dw/layout.cc')
-rw-r--r--dw/layout.cc3
1 files changed, 3 insertions, 0 deletions
diff --git a/dw/layout.cc b/dw/layout.cc
index 3680e0c8..d1fecf48 100644
--- a/dw/layout.cc
+++ b/dw/layout.cc
@@ -852,6 +852,9 @@ void Layout::moveToWidget (Widget *newWidgetAtPoint, ButtonState state)
int trackLen, i;
EventCrossing crossingEvent;
+ if (!topLevel)
+ return;
+
if (newWidgetAtPoint != widgetAtPoint) {
// The mouse pointer has been moved into another widget.
if (newWidgetAtPoint && widgetAtPoint)