1. 07 Oct, 2018 1 commit
    • Hugo Lefeuvre's avatar
      gtkstack: fix null pointer dereference · adbaee79
      Hugo Lefeuvre authored and Daniel Boles's avatar Daniel Boles committed
      The gtk_stack_snapshot_slide() function dereferences the
      last_visible_child pointer without proper != NULL ckeck. This might
      result in NULL pointer dereference and crash if last_visible_child is
      invalid.
      
      Add a != NULL check before dereferencing the pointer.
      
      cherry-picked from !361
      adbaee79
  2. 19 Apr, 2018 1 commit
  3. 14 Nov, 2016 1 commit
  4. 30 May, 2016 1 commit
  5. 20 May, 2016 1 commit
    • Florian Müllner's avatar
      stack: Only map children when necessary · 57efcabf
      Florian Müllner authored
      gtk_widget_set_parent() will map the widget if the parent is mapped
      and the widget is both visible and child-visible. As we currently
      only set the child visibility after adding the child, we immediately
      map all children that are added to a mapped stack, even when they
      are not actually shown. Avoid this by setting the child visibility
      before adding the child, so widgets are only mapped when shown.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=766737
      57efcabf
  6. 16 May, 2016 1 commit
  7. 12 May, 2016 2 commits
  8. 01 May, 2016 1 commit
  9. 08 Apr, 2016 2 commits
    • Matt Watson's avatar
      stack: skip first frame for animations · 62b224a8
      Matt Watson authored
      Not the ideal solution for this problem, but in practice leads to
      much better performance on lower end hardware.
      
      Stack does a double draw on the first frame of its animation, of
      both the old contents (into a cairo surface) and the new contents.
      Homogeneous stacks only need to reallocate contents on the first
      frame.
      
      On lower powered hardware where our frames will be a good deal
      slower than the refresh rate anyway, we can assure a smother
      experience by waiting a frame to start tweening where frame duration
      will be more consistent.
      62b224a8
    • Matt Watson's avatar
      stack: port to progress tracker · 3909f818
      Matt Watson authored
      3909f818
  10. 21 Mar, 2016 1 commit
  11. 28 Feb, 2016 1 commit
  12. 08 Feb, 2016 1 commit
    • Timm Bäder's avatar
      Various documentation fixes · c5369356
      Timm Bäder authored
      Always have Since: annotations at the very bottom, use the correct
      ClassName::signal-name/ClassName:property-name syntax, fix a few typos
      in type names, wrong function names, non-existing type names, etc.
      c5369356
  13. 26 Jan, 2016 2 commits
  14. 22 Jan, 2016 1 commit
  15. 19 Jan, 2016 1 commit
  16. 15 Dec, 2015 2 commits
  17. 11 Dec, 2015 1 commit
  18. 30 Nov, 2015 1 commit
  19. 24 Nov, 2015 1 commit
  20. 19 Nov, 2015 1 commit
    • Carlos Soriano Sánchez's avatar
      gtkstack: allow templates to override all properties · 9f383906
      Carlos Soriano Sánchez authored and Matthias Clasen's avatar Matthias Clasen committed
      Currently GtkStack has some G_PARAM_CONSTRUCT properties. That means,
      the properties are set with its default value after the initializacion
      of the object.
      When using GtkBuilder to build objects, GtkBuilder creates them and
      after that sets the properties found on the xml definition.
      However, this is not true for templates because the template is initialized
      in the init() function of the actual object, and after that, the construct
      properties will be set.
      
      This is a problem when someone wants to use templates with GtkStack and
      set those properties, since they will be set on the tempalt initialization
      and set again to its default values afterwards.
      
      To fix this, make those properties not G_PARAM_CONSTRUCT.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=758086
      9f383906
  21. 09 Nov, 2015 1 commit
  22. 05 Nov, 2015 1 commit
  23. 04 Nov, 2015 2 commits
  24. 03 Nov, 2015 1 commit
  25. 14 Sep, 2015 1 commit
    • Alexander Larsson's avatar
      gtk: Stop setting GDK_EXPOSURE_MASK on random widgets · d5f17549
      Alexander Larsson authored
      These days exposure happens only on the native windows (generally the
      toplevel window) and is propagated down recursively. The expose event
      is only useful for backwards compat, and in fact, for double buffered
      widgets we totally ignore the event (and non-double buffering breaks
      on wayland).
      
      So, by not setting the mask we avoid emitting these events and then
      later ignoring them.
      
      We still keep it on eventbox, fixed and layout as these are used
      in weird ways that want backwards compat.
      d5f17549
  26. 08 Sep, 2015 1 commit
  27. 09 Aug, 2015 1 commit
  28. 05 Aug, 2015 1 commit
  29. 20 Jul, 2015 2 commits
  30. 23 Jun, 2015 1 commit
  31. 21 Jun, 2015 1 commit
    • Paolo Borelli's avatar
      Avoid spurious operations on destroy · 4e155d78
      Paolo Borelli authored and Matthias Clasen's avatar Matthias Clasen committed
      When the stack is destroyed we do not want to waste time running
      animations and notifying listeners about which is our current
      visible child.
      
      This is not only an optimization, but it is important for the stack
      switcher widgets: since they are in another branch of the hieratchy
      we do not want to get notifications while the stack is being destroyed.
      
      Based on a patch by Paolo Borelli
      https://bugzilla.gnome.org/show_bug.cgi?id=724506
      4e155d78
  32. 30 May, 2015 1 commit
  33. 29 May, 2015 2 commits