1. 08 Apr, 2013 1 commit
    • Tristan Van Berkom's avatar
      Deprecate gtk_widget_push_composite_child & friends · c6ab5157
      Tristan Van Berkom authored
      Deprecate gtk_widget_push_composite_child, gtk_widget_pop_composite_child,
      gtk_widget_set_composite_name, gtk_widget_get_composite_name.
      
      This API is just bloat and was never useful, this patch deprecates
      it and removes all internal calls to the composite child APIs
      c6ab5157
  2. 07 Feb, 2013 1 commit
    • Alexander Larsson's avatar
      Add gtk_widget_(un)register_window · 3d4cd4db
      Alexander Larsson authored
      This replaces the previously hardcoded calls to gdk_window_set_user_data,
      and also lets us track which windows are a part of a widget. Old code
      should continue working as is, but new features that require the
      windows may not work perfectly.
      
      We need this for the transparent widget support to work, as we need
      to specially mark the windows of child widgets.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=687842
      3d4cd4db
  3. 17 Jan, 2013 2 commits
  4. 16 Jan, 2013 1 commit
  5. 15 Jan, 2013 2 commits
    • John Lindgren's avatar
      Use minimum/natural size semantics · 6d53c233
      John Lindgren authored
      Rewrites gtk_tree_view_column_request_width() and
      gtk_tree_view_size_allocate_columns() to respect the minimum and natural
      sizes that are already being returned by
      gtk_cell_area_context_get_preferred_width().
      
      The convoluted logic explained (not!) by this comment has been removed:
      “Only update the expand value if the width of the widget has changed, or
      the number of expand columns has changed, or if there are no expand
      columns, or if we didn't have an size-allocation yet after the last
      validated node.”  This logic seems to have been a workaround for the
      “jumping” behavior fixed in 16195adc and is no longer necessary.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=691751
      6d53c233
    • John Lindgren's avatar
      Use fixed width for resizing · 16195adc
      John Lindgren authored
      Removes the hidden “resized-width” and “use-resized-width” properties
      from GtkTreeViewColumn and instead uses the “fixed-width” property to
      serve the same purpose.  “fixed-width”, if set, will now override the
      auto-sized width (-1 is now a legal value meaning “not set”).
      
      Additional “cleanups” in this commit:
      
      1. When the user resizes the column the “expand” property is now also
      set to FALSE, in order to prevent the column from suddenly jumping to a
      different width when the window is resized.
      
      2. The code that translated mouse movement to column sizes has been
      simplified:
      the change in column width is now calculated directly from the distance
      the mouse cursor has traveled.  Weird behavior that might have happened
      previously if the position of the column changed during resizing, is now
      prevented.
      
      3. There was some lengthy logic handling the keyboard shortcuts used to
      resize treeview columns, which would call gtk_widget_error_bell() once
      the minimum or maximum width was reached.  Instead of rewriting these
      checks I simply set the “fixed-width” property to what was requested,
      relying on the fact that it is already clamped between the minimum and
      maximum width during size allocation.
      I will greatly surprised if anyone notices the missing error bell.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=691751
      16195adc
  6. 08 Jan, 2013 1 commit
  7. 27 Dec, 2012 1 commit
    • Matthias Clasen's avatar
      Make accessible implementations public · e4b5e94e
      Matthias Clasen authored
      This commit exposes the get_type() functions and standard
      headers for accessible implementations. This makes it possible
      to derive from the GTK accessible implementations without
      GType magic tricks. This is necessary, because we require the
      a11y type hierarchy to be parallel to the widget type hierarchy.
      So, if you derive a widget and need to adjust its a11y implementation,
      you have to be able to derive its accessible implementation.
      
      This commit probably exposes more than is absolutely necessary,
      it also exposes accessibles of widgets that are unlikely candidates
      for deriving from.
      e4b5e94e
  8. 02 Jul, 2012 1 commit
  9. 27 Feb, 2012 1 commit
  10. 20 Feb, 2012 1 commit
  11. 27 Jan, 2012 1 commit
  12. 16 Nov, 2011 1 commit
    • Benjamin Otte's avatar
      treeview: Call a11y functions for culmn changes directly · a4b88c47
      Benjamin Otte authored
      This way, the a11y code knows if a column was reordered, added or
      removed and can do the right things instead of trying to guess and
      getting it wrong.
      
      Also, this patch finalizes the changes so that only visible columns
      exist to the accessibility interface.
      a4b88c47
  13. 02 Nov, 2011 1 commit
  14. 06 Oct, 2011 1 commit
  15. 29 Sep, 2011 1 commit
    • Cosimo Cecchi's avatar
      GtkTreeViewColumn: initialize a variable · fb488d49
      Cosimo Cecchi authored
      Shut up valgrind complaining about uninitialized values
      
      ==5330== Conditional jump or move depends on uninitialised value(s)
      ==5330==    at 0x624FF4C: gdk_window_move_resize_internal
      (gdkwindow.c:6037)
      ==5330==    by 0x62502C3: gdk_window_move_resize (gdkwindow.c:6274)
      ==5330==    by 0x5E4FBB5: _gtk_tree_view_column_allocate
      (gtktreeviewcolumn.c:2169)
      ==5330==    by 0x5E3846B: gtk_tree_view_size_allocate_columns
      (gtktreeview.c:2631)
      ==5330==    by 0x5E43D76: gtk_tree_view_size_allocate
      (gtktreeview.c:2686)
      ==5330==    by 0x7F03959: g_closure_invoke (gclosure.c:774)
      ==5330==    by 0x7F16446: signal_emit_unlocked_R (gsignal.c:3202)
      ==5330==    by 0x7F20256: g_signal_emit_valist (gsignal.c:3003)
      ==5330==    by 0x7F20421: g_signal_emit (gsignal.c:3060)
      ==5330==    by 0x5E6DFBE: gtk_widget_size_allocate (gtkwidget.c:4886)
      ==5330==    by 0x5D94ADD: gtk_scrolled_window_allocate_child
      (gtkscrolledwindow.c:1506)
      ==5330==    by 0x5D95299: gtk_scrolled_window_size_allocate
      (gtkscrolledwindow.c:1704)
      ==5330==    by 0x7F03959: g_closure_invoke (gclosure.c:774)
      ==5330==    by 0x7F16446: signal_emit_unlocked_R (gsignal.c:3202)
      ==5330==    by 0x7F20256: g_signal_emit_valist (gsignal.c:3003)
      ==5330==    by 0x7F20421: g_signal_emit (gsignal.c:3060)
      ==5330==    by 0x5E6DFBE: gtk_widget_size_allocate (gtkwidget.c:4886)
      ==5330==    by 0x5C62708: gtk_box_size_allocate (gtkbox.c:658)
      ==5330==    by 0x7F03959: g_closure_invoke (gclosure.c:774)
      ==5330==    by 0x7F16446: signal_emit_unlocked_R (gsignal.c:3202)
      ==5330==  Uninitialised value was created by a stack allocation
      ==5330==    at 0x5E4FA8D: _gtk_tree_view_column_allocate
      (gtktreeviewcolumn.c:2139)
      fb488d49
  16. 26 Sep, 2011 1 commit
  17. 25 Sep, 2011 2 commits
  18. 28 Aug, 2011 1 commit
  19. 10 Jun, 2011 2 commits
  20. 09 Jun, 2011 1 commit
  21. 16 Apr, 2011 1 commit
  22. 24 Feb, 2011 1 commit
  23. 23 Feb, 2011 1 commit
  24. 05 Feb, 2011 1 commit
  25. 03 Feb, 2011 1 commit
  26. 31 Jan, 2011 1 commit
  27. 27 Jan, 2011 2 commits
    • Carlos Garnacho's avatar
      Make GtkTreeView use GtkStyleContext · 08af1783
      Carlos Garnacho authored
      Expander animation has been replaced by implicit animations
      from the style context.
      
      Column headers are also properly themed, GtkContainer::get_path_for_child()
      is implemented and the treeview resets column buttons style on columns
      being reordered.
      
      The default CSS has changed to theme treeviews sensibly.
      08af1783
    • Carlos Garnacho's avatar
      Make GtkCellArea use GtkStyleContext · 41d6837f
      Carlos Garnacho authored
      gtk_cell_area_[gs]et_style_detail() is no longer needed, as
      the passed widget's context would already have all necessary
      info.
      41d6837f
  28. 20 Jan, 2011 1 commit
  29. 18 Jan, 2011 1 commit
  30. 07 Jan, 2011 2 commits
  31. 04 Jan, 2011 1 commit
  32. 23 Dec, 2010 1 commit
  33. 21 Dec, 2010 1 commit
  34. 15 Dec, 2010 1 commit
    • Kristian Rietveld's avatar
      Revisit "Handle clicks in indentation area" · c8d130ef
      Kristian Rietveld authored
      Check (x, y) is inside background area.  If yes, continue processing
      and clamp the coordinates into cell area.  This way we will properly
      handle getting a cell (which is only used for setting the focus cell)
      for clicks in the indentation area (in LTR and RTL mode) and clicks
      in the focus rectangle area in case focus-line-width is large.
      c8d130ef