1. 04 Jun, 2014 1 commit
  2. 03 Jun, 2014 22 commits
  3. 02 Jun, 2014 4 commits
    • Carlos Garnacho's avatar
      window: Only check for the event widget if clicked on the "content" region · 3c0ebf65
      Carlos Garnacho authored
      Every button press/release event reaching the the multipress gesture in GtkWindow
      and happening in the "title" region must be handled, regardless of the event widget.
      Children there wanting the event(s) for themselves are (and were always) expected
      to stop event propagation.
      
      So the only place to check for the event widget's "window-dragging" style property
      is the "content" region, which matches the pre-gestures behavior.
      
      This fixes some issues with sequences being mistakenly claimed (and events not
      propagated further) on situations it shouldn't.
      3c0ebf65
    • Carlos Garnacho's avatar
      window: Handle manually bubbled events · 00656ed1
      Carlos Garnacho authored
      The multipress gesture must react to either direct events on the
      GtkWindow (special cased through _gtk_widget_check_handle_wm_event),
      or bubbled events from child widgets. Ensure bubbled events go
      through the gesture, those are fed manually to make sure events are
      only handled once, in either one or other place. The implicit grab
      will ensure that doesn't change mid-action.
      00656ed1
    • Carlos Garnacho's avatar
      window: Refactor _gtk_window_check_handle_wm_event() · 7f33706c
      Carlos Garnacho authored
      Separate the event widget check from event handling
      7f33706c
    • Carlos Garnacho's avatar
      treeview: Ensure the event is consumed on ::row-activate · e1c425a2
      Carlos Garnacho authored
      Otherwise the event is possibly handled, but still propagated further anyway.
      Ensure the event is consumed by claiming the current sequence on the
      GtkGestureMultiPress::pressed handler.
      e1c425a2
  4. 01 Jun, 2014 5 commits
  5. 31 May, 2014 8 commits