1. 29 Oct, 2014 2 commits
  2. 28 Oct, 2014 1 commit
    • Matthias Clasen's avatar
      wayland: Make window opacity work · 4cf6edda
      Matthias Clasen authored
      Under wayland, the compositor doesn't have a 'overall window alpha'
      knob, we just need to add the alpha to the buffers we send.
      Client-side alpha, if you want to call it that.
      
      Implement this by reusing the existing alpha support for non-toplevel
      widgets. As a side-effect of the implementation, windows with RGBA
      visual under X will now also use per-pixel alpha, instead of
      overall alpha.
      4cf6edda
  3. 24 Oct, 2014 1 commit
  4. 21 Oct, 2014 1 commit
  5. 20 Oct, 2014 2 commits
  6. 13 Oct, 2014 1 commit
  7. 30 Sep, 2014 1 commit
  8. 06 Sep, 2014 2 commits
  9. 27 Aug, 2014 1 commit
  10. 20 Aug, 2014 1 commit
  11. 18 Aug, 2014 2 commits
  12. 17 Aug, 2014 1 commit
  13. 16 Aug, 2014 2 commits
  14. 12 Aug, 2014 1 commit
  15. 09 Aug, 2014 1 commit
  16. 19 Jul, 2014 1 commit
  17. 10 Jul, 2014 1 commit
  18. 03 Jul, 2014 1 commit
  19. 26 Jun, 2014 1 commit
    • Emmanuele Bassi's avatar
      docs: Show examples of how to use templates API · 5b571ff4
      Emmanuele Bassi authored
      The template documentation is lacking inlined examples on how to use the
      templates API, like binding children and callbacks. This makes looking
      for best practices a bit harder than it ought to be, for a feature this
      useful.
      5b571ff4
  20. 23 Jun, 2014 2 commits
  21. 22 Jun, 2014 1 commit
  22. 21 Jun, 2014 2 commits
  23. 10 Jun, 2014 1 commit
  24. 09 Jun, 2014 1 commit
    • Matthias Clasen's avatar
      GtkWidget: Use G_PARAM_EXPLICIT_NOTIFY · acad03f7
      Matthias Clasen authored
      A few properties here are special, and can't benefit from it:
      those which are just shorthands, like ::margin and ::expand,
      and those that have explicit -set properties, like::hexpand
      and ::vexpand.
      acad03f7
  25. 05 Jun, 2014 1 commit
  26. 04 Jun, 2014 1 commit
  27. 03 Jun, 2014 2 commits
    • Carlos Garnacho's avatar
      widget: Ensure all gestures outside a grab scope are cancelled · 25f5da50
      Carlos Garnacho authored
      This code is a product of early stages in the gestures branch, where
      capturing would have an effect outside grab boundaries. But this isn't
      really the case, so every gesture outside the grab scope must be reset
      to avoid keeping stale data.
      25f5da50
    • Carlos Garnacho's avatar
      widget: Only deny a sequence if it was previously claimed · 26ced6ab
      Carlos Garnacho authored
      Before this change, a sequence being claimed deep in the event propagation
      chain would make the sequence go denied on every ancestor, regardless of
      previous state.
      
      To make things more consistent, only deny the sequence if it was previously
      claimed, so the behavior is the same for gesture groups within the widget
      than for those outside the widget.
      
      The gestures testsuite has been updated to reflect this new behavior.
      26ced6ab
  28. 31 May, 2014 1 commit
  29. 30 May, 2014 1 commit
  30. 28 May, 2014 2 commits
  31. 27 May, 2014 1 commit
    • Carlos Garnacho's avatar
      widget: Change GtkCapturePhase behavior in event controllers' handling · 505efbb3
      Carlos Garnacho authored
      Previously, there would be globally just a capture and a bubble phase,
      with the event just going down the hierarchy once, and the up once.
      GTK_PHASE_TARGET actually meaning "run within event handlers", so in
      a hierarchy of 3 widgets, emission would be:
      
        Capture(C)
        Capture(B)
        Capture(A)
        Target(A) (if event handlers allow)
        Bubble(A)
        Target(B) (if event handlers allow)
        Bubble(B)
        Target(C) (if event handlers allow)
        Bubble(C)
      
      This commit changes this behavior and uses GTK_PHASE_TARGET in a less
      misleading way, running only on the widget that was meant to receive
      the event. And GTK_PHASE_BUBBLE has taken over the execution place of
      GTK_PHASE_TARGET, so the emission remains:
      
        Capture(C)
        Capture(B)
        Capture(A)
        Target(A)
        Bubble(A) (if event handlers allow)
        Bubble(B) (...)
        Bubble(C) (...)
      
      As it was, GTK_PHASE_BUBBLE was useful for running event controllers
      paralelly to event handlers, without modifying a single line in those.
      For those mixed scenarios, Any of the other phases will have to be
      used at discretion, or the event handlers eventually changed to chain
      up and let the default event handlers in GtkWidget to be run.
      505efbb3