2010/2/10 Krzysztof Kosiński <tweenk.pl@...400...>:
switch (event->type) { case GDK_MOTION_NOTIFY: {
- if (event->button.button == 1) {
combine_motion_events(desktop->canvas, event->motion, 0);
Uh, that only works by accident, and it breaks the highlighting of paths. Why do you want to check for a field in the button structure, if what you've got is the motion structure? In other words you have a GdkEventMotion but access it as a GdkEventButton.
Yep, sorry, I just copied that check from select-context without checking event type.
It looks like this check actually checks is_hint. is_hint is always false because as far as I know we do not use GDK_POINTER_MOTION_HINT_MASK. What you're looking for is probably changing "return true;" at the end of this case to "return false;", so that the motion event is always passed further up. I did this in 9081.
I didn't want to change behavior for button ==1. If it returns true, let it return true. Just don't gobble other buttons, that's all :)
Now that I see it I also have no idea how it worked for me before.
:)