[maemo-developers] Problem with Treeview drag and drop

[From: Jeffrey Barish]

As I reported a month ago, I am having a problem with Treeview drag and
drop.  I am not able to pick up a row unless I trace out of the treeview.

I discovered something interesting today.  I am catching motion-notify-event
and printing out the position of the event.  I observe that with a fresh
treeview, I get a barrage of new event positions as I move the stylus in
the treeview -- as expected.  Then I drag a row from another treeview and
drop it in the treeview in question.  At that point, tracing on the
remaining open space elicits exactly two events, the initial tap and one
motion event.  If I am aggressive, I can sometimes move the stylus quickly
enough that the one motion event is far enough from the initial tap to
trigger the drag.  It's clear that I can't pick up a row because gtk is not
registering stylus movement -- until I move it out of the treeview.  But
why would it happen that I would stop receiving motion events after
dropping into the treeview?  I do not get this behavior when I run the
program on Ubuntu.  Can anyone suggest a way to "reset" the treeview so
that it starts receiving motion events again?

Here's more: The drag from the source treeview doesn't start until the
stylus exits the treeview.  I investigated further and discovered that the
same problem occurs there.  So it isn't just dragging something into the
treeview that initiates the problem, it's also writing something into the
treeview programmatically.  A test program that I wrote does not
demonstrate the problem, so it seems that something is wrong with my code,
but I am at a loss as to what to look for.  Moreover, if something is wrong
with my code, it seems odd that it works fine on Ubuntu.
-- 
Jeffrey Barish