1. 26 Jan, 2010 4 commits
  2. 25 Jan, 2010 4 commits
  3. 23 Jan, 2010 1 commit
  4. 22 Jan, 2010 5 commits
    • Paul Davis's avatar
      Small memory fix · 7767dae9
      Paul Davis authored
      7767dae9
    • Michael Natterer's avatar
      Bug 607778 - Add accessors for GtkEntry's windows · 2f9c4be0
      Michael Natterer authored
      Add gtk_entry_get_text_window() and get_icon_window() so we can
      distinguigh them in expose-event callbacks.
      2f9c4be0
    • Michael Natterer's avatar
      Bug 607082 - Add accessors for sealed GtkRange members · 35a2b653
      Michael Natterer authored
      Add accessors for range->range_rect, range->slider_range,
      range->slider_size_fixed and range->min_slider_size. Didn't add
      properties for any of them because thir purpose is mostly to enable
      proper subclassing.
      35a2b653
    • Claudio Saavedra's avatar
      GtkTreeView: plug a leaking GtkTreeRowReference · 52acceef
      Claudio Saavedra authored
      This is exposed by overshooting in a HildonPannableArea. Leaking
      a GtkTreeRowReference also means leaking the whole model, since
      the GtkTreeModel reference count is increased for each row
      reference.
      
      Fixes bug #607770 - Leak in GtkTreeView with HildonPannableArea
      52acceef
    • Alexander Larsson's avatar
      Avoid integer overflow in gdk_rectangle_intersect · 3c618f2f
      Alexander Larsson authored
      If e.g. the right edge of the leftmost rectangle is near MIN_INT, and
      the left edge of the rightmost rectangle is large then subtracting these
      can lead to an integer overflow, making the resultant "width" falsely
      positive, thus returning a very wide result instead of the expected
      no-intersection result.
      
      We avoid the overflow by not doing the subtraction unless we know the
      result will be positive. There are still risks for overflow if x + width
      or y + width is larger than MAXINT, but we won't ever overflow for valid
      rects now.
      
      This may fix #607687
      3c618f2f
  5. 20 Jan, 2010 2 commits
  6. 19 Jan, 2010 11 commits
  7. 18 Jan, 2010 8 commits
  8. 16 Jan, 2010 1 commit
  9. 15 Jan, 2010 4 commits