1. 12 Dec, 2015 1 commit
  2. 06 Sep, 2015 1 commit
  3. 31 Jul, 2015 1 commit
  4. 13 Apr, 2015 1 commit
    • Carlos Garnacho's avatar
      gesturesingle: Ignore motion/updates from unhandled sequences · 8bf5b175
      Carlos Garnacho authored
      This used to do the right thing, practically ignoring those event
      if they went all through the event handler, unless this motion event
      triggered the cancellation of this gesture from the event handler
      of another controllers.
      
      In this case, the controller would be reset, but the motion event
      would still go through its handler, setting again
      current_button/sequence as the motion event has buttons in its
      modifiers. This leaves GtkGestureSingle with inconsistent data
      that may interfere with future runs.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=747469
      8bf5b175
  5. 18 Dec, 2014 1 commit
    • Carlos Garnacho's avatar
      gesturesingle: check for the sequence being handled, not just the event · dca2f438
      Carlos Garnacho authored
      Checking the return value was valid for most gestures, but
      GtkGestureLongPress, where the first press triggers internally an action,
      but does nothing for the sequence to be claimed/denied, FALSE was eventually
      returned, and the button/sequence functions would be incorrect when
      ::pressed is emitted.
      
      So check that the sequence is being handled by the gesture, this is more
      desirable than the return value as it's independent of sequence state,
      and still will be FALSE for the cases we want to catch here.
      dca2f438
  6. 17 Oct, 2014 1 commit
  7. 26 Aug, 2014 1 commit
  8. 15 Aug, 2014 2 commits
  9. 10 Jul, 2014 1 commit
  10. 12 Jun, 2014 1 commit
    • Carlos Garnacho's avatar
      gesturesingle: Implement GtkGesture::cancel better than GtkEventController:reset · 6d8842ca
      Carlos Garnacho authored
      The former can be called individually on each sequence, and the latter will
      always call the former on all currently active sequences, so only implementing
      resetting on cancel() works for both cases. Also, chain up on subclasses
      implementing cancel.
      
      This fixes clicking on nautilus' file list after popping up a menu, as broken
      grabs are one of those situations where sequences get cancelled individually,
      the "current button" wasn't properly reset, and further clicks with button != 3
      were ignored.
      6d8842ca
  11. 11 Jun, 2014 1 commit
  12. 09 Jun, 2014 1 commit
  13. 23 May, 2014 9 commits