| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Clarify the use of brackets in the CSS node diagrams:
[] means optional nodes or classes, <> means child widgets.
|
| |
|
| |
|
| |
|
|
|
|
| |
For the same reasons as g_object_child_notify_by_pspec.
|
|
|
|
|
| |
This lets us use inlined getters for members in there,
avoiding the type checks in the public getters.
|
|
|
|
|
|
| |
This reverts commit e215db6da21fc7c54f49b247afabc06a18d60513.
We are actually requiring non-NULL out arguments here now.
|
|
|
|
| |
Coverity complained about these.
|
| |
|
| |
|
|
|
|
|
| |
This was an omission, horizontal/vertical would only be set
when the orientation is changed.
|
| |
|
|
|
|
| |
... and use it in GtkBox and GtkGrid.
|
| |
|
|
|
|
|
| |
Size vfuncs always get non-null out variables passed, so no need to
check for NULL.
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
| |
|
|
|
|
| |
The previous commit was misapplied.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=634793
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711324
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702996
|
|
|
|
|
|
|
| |
Revert 5e1a06d1b124f09a1a54d5ae0f38905dbdc2cc81
This change caused empty rows to 'open up', which was not
intended and causes problems as seen in bug 698660.
|
| |
|
| |
|
|
|
|
|
| |
We support a local baseline in each row, as well as selecting
a specific row for the global baseline of the entire GtkGrid.
|
|
|
|
|
|
| |
It is sometimes convenient to deal with entire rows or
columns at a time.
https://bugzilla.gnome.org/show_bug.cgi?id=695994
|
|
|
|
|
|
|
|
|
|
| |
If there are rows that contain only spanning children,
our algorithm was unnecessarily distributing extra space
to the other rows, even if they contain only non-expanding
children.
We improve the behaviour by treating rows containing only
spanning children as expanding.
|
|
|
|
|
|
| |
The priv member should be accessed after the g_return_if_fail test
https://bugzilla.gnome.org/show_bug.cgi?id=677363
|
|
|
|
|
|
| |
Add missing guard to make sure it's called with a GtkGrid argument.
https://bugzilla.gnome.org/show_bug.cgi?id=677363
|
|
|
|
|
| |
gtk_grid_get_child_at() is missing a transfer annotation for the returned
widget, making it not introspectable.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=669989
|
|
|
|
|
|
|
|
| |
When a homogeneous grid has no visible children, we were
accidentally doing a division by zero. Instead, just bail
out early in this case, there is nothing to allocate anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=672763
|
|
|
|
|
|
|
|
|
| |
When doing homogeneous allocation in the presence of
overlapping spanning children, we need to avoid uneven
line allocations, otherwise, the final homogenization
will blow up the size request of the grid.
https://bugzilla.gnome.org/show_bug.cgi?id=671170
|
| |
|
|
|
|
|
| |
The function did not behave as intended when @sibling is NULL.
Also add an example to the docs to clarify the intended behaviour.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=660139
|
| |
|
|
|
|
|
|
|
|
| |
row-spacing behaved like column-spacing should have and vice versa.
Also update tests that erroneously checked this behavior.
Thanks to Joanmarie Diggs for finding this.
|
|
|
|
|
|
|
| |
Allow to attach children at either end of row/column 0.
Proposed by Alex Larsson.
https://bugzilla.gnome.org/show_bug.cgi?id=657793
|
|
|
|
| |
This addresses concerns in bug 634136.
|
|
|
|
|
|
|
| |
This is useful functionality that makes it easier to insert
things in the middle of an already populated grid.
Bug 653817
|
|
|
|
|
|
|
|
|
| |
We need pay attention the the request mode when doing size allocation.
The code was using request mode for requisition, but orientation
for allocation.
Also add a reftest that exhibits the issue, courtesy of
Benjamin Otte.
|
|
|
|
|
|
| |
Not that we are doing too much work in that case, but we are
segfaulting, which is bad.
https://bugzilla.gnome.org/show_bug.cgi?id=649972
|
| |
|
|
|
|
| |
How did we manage to add a non-RTL savy container in GTK+ 3.0 ?
|
|
|
|
|
|
|
| |
The constant size request mode defines a request mode where
height-for-width geometry is unneeded, thus optimizing GTK+
by reducing the overall amount of requests that need to be
performed and cached while resizing an interface.
|
|
|
|
|
| |
valgrind complained about these, and they make for bad size allocation
and the occasional crash.
|
| |
|
|
|
|
|
| |
Add a _gtk_orientable_set_style_classes() function so all
orientation changes to style happen in a single place.
|