1. 04 Feb, 2010 5 commits
  2. 02 Feb, 2010 1 commit
  3. 01 Feb, 2010 3 commits
  4. 31 Jan, 2010 2 commits
  5. 30 Jan, 2010 4 commits
    • Kristian Rietveld's avatar
      Improve enter/motion notify semantics · 66207cf1
      Kristian Rietveld authored
      On X11 we receive enter notify and motion notify events for a window
      regardless of its focus state.  On Mac OS X this is not the case.  This
      commit improves the semantics to overcome this difference.  It improves
      on my earlier patch that sent a motion notify event when a window became
      Instead of sending a motion notify when a window becomes main, we now
      send one when a window becomes key, which comes closest to a window
      getting focus in X11.  This motion notify is needed because Mac OS X does
      not send motion events when an application is inactive (none of its
      windows have focus), these events are sent in X11.  This dummy motion
      notify event (with current coordinates of the mouse cursor) allows an
      application to get its prelight and other state right when it gets focus
      and thus user attention.
      Another change is to send an enter notify event when updating the
      tracking rectangle of a GdkQuartView and the mouse cursor is currently in
      this rectangle.  This rectangle is at least updated on window creation.
      This enter notify event is important for the case where a new window
      appears right below the mouse cursor.  The window has to receive an enter
      notify event for the subsequent events to be processed correctly.  Mac
      OS X does not send one in this case, so we generate it ourselves.
      Both of these synthesized events have to go through
      _gdk_windowing_got_event() for updating statekeeping, etc.
      append_event() has a boolean flag now to make this convenient.
    • Jorge González's avatar
      Updated Spanish translation · 15ef288b
      Jorge González authored
    • Jorge González's avatar
      Updated Spanish translation · f0005fb9
      Jorge González authored
    • Jorge González's avatar
      Updated Spanish translation · a5d7a7a6
      Jorge González authored
  6. 29 Jan, 2010 6 commits
  7. 28 Jan, 2010 4 commits
  8. 26 Jan, 2010 5 commits
  9. 25 Jan, 2010 4 commits
  10. 23 Jan, 2010 1 commit
  11. 22 Jan, 2010 5 commits
    • Paul Davis's avatar
      Small memory fix · 7767dae9
      Paul Davis authored
    • 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.
    • 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.
    • 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
      Fixes bug #607770 - Leak in GtkTreeView with HildonPannableArea
    • 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