- 19 Feb, 2014 20 commits
-
-
William Jon McCann authored
Instead of Return value:
-
Kjartan Maraas authored
-
Yuri Myasoedov authored
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
Similar to map/unmap, this needs to follow the actual widget tree. Without this, several test cases in the templates test fail.
-
Matthias Clasen authored
-
Matthias Clasen authored
These were added to the header by mistake in a recent commit. They have no implementation, so dropping them won't cause any harm.
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
GtkPrintUnixDialog was leaking a GFile. Spotted by Christian Persch in https://bugzilla.gnome.org/show_bug.cgi?id=724631
-
Carlos Garnacho authored
And document the fact that the popover will get destroyed if a NULL relative-to is given on a parented popover, if no extra references are kept. For gtk_popover_new*(), a NULL relative-to will leave the widget as a floating object, to be sunk by a later call to gtk_widget_set_relative_to(). https://bugzilla.gnome.org/show_bug.cgi?id=724407
-
Paolo Borelli authored
This gives a critical warning since that function expects a valid widget. https://bugzilla.gnome.org/show_bug.cgi?id=724407
-
Matthias Clasen authored
Use a weak reference to notice when parent_scrollable is going away. https://bugzilla.gnome.org/show_bug.cgi?id=724392
-
Matthias Clasen authored
This error was causing children to not get allocated when the center widget is the first one in the list of the box's children.
-
Matthias Clasen authored
It makes sense to allow this, and gtk_action_bar_set_center_widget already assumes that it can pass NULL to this function.
-
Matthias Clasen authored
The recursion in map needs to follow the actual physical widget tree, otherwise we violate invariants. The generic container map implementation uses gtk_container_forall to operate on the children, and thus is not suitable for containers where the children are inside some internal container.
-
Matthias Clasen authored
We need to always iterate over non-internal children.
-
Matthias Clasen authored
This reverts commit 0ff0fdfe.
-
Paolo Borelli authored
This is needed to set a padding and draw a border since GtkBox does not honour css padding yet. https://bugzilla.gnome.org/show_bug.cgi?id=724693
-
- 18 Feb, 2014 18 commits
-
-
Jasper St. Pierre authored
-
Jasper St. Pierre authored
-
Javier Jardón authored
-
Matthias Clasen authored
-
Ignacio Casal Quinteiro authored
-
Matthias Clasen authored
-
Matthias Clasen authored
This broke recently when the window dragging code was changed to require motion events to be propagated as well. https://bugzilla.gnome.org/show_bug.cgi?id=724539
-
Matthias Clasen authored
This makes them draggable, and is the right thing to do.
-
Matthias Clasen authored
We should only eat button release events when the label is actually selectable, since the comment indicates that we want to eat the release events belonging to press events that triggered a selection. This fixes problems with actions on parent widgets that are triggered by button release, as seen in this bug: https://bugzilla.gnome.org/show_bug.cgi?id=724541
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
GtkActionBar and GtkSearchBar also use templates, add them here.
-
Matthias Clasen authored
Suprisingly, this bug has been there for a very long time. I'm fixing it now because we now use a custom search entry in the app chooser dialog, and this is causing the templates cleanup test to fail.
-
Matthias Clasen authored
This was also causing the templates test to fail.
-
Matthias Clasen authored
With nested internal children, this interferes with proper cleanup, and makes the templates test fail.
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
-
- 17 Feb, 2014 2 commits
-
-
Paolo Borelli authored
-
Yuri Myasoedov authored
-