| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Redo this series of examples from 2013, and adapt it to modern
way of doing things. The biggest differences are that we use
a headerbar right from the start, and don't mention the app
menu.
Fixes: #2730
|
|
|
|
|
| |
The fallback to the menubar is not a good sight,
we should not do that by default.
|
|
|
|
|
|
| |
Since the meson conversion, we are no longer expanding
gtk-doc references in this file, so take them out. And
touch up the wording in various places.
|
|
|
|
|
|
|
| |
One of the treeview tests was calling gtk_widget_destroy
on a child instead of the toplevel, which leaks the toplevel
unnecessarily. Plus, we're moving towards allowing destroy
only on toplevels.
|
|
|
|
| |
Don't call your boxes frames, folks!
|
|
|
|
|
|
| |
Don't chain up to dispose if you implement finalize.
This fix s courtesy of GOBJECT_DEBUG=objects.
|
|
|
|
|
| |
It is a bad idea to have a GtkBox called frame, event
if it started out its existence as a GtkFrame.
|
|
|
|
|
|
|
|
|
|
| |
The css tree and the widget tree are not in sync, so we need
to explicitly set the parent of the css node before inserting
the widget, or else we end up with critical warnings and a
non-working popover.
This can be seen in the print dialog, when moving the focus
to the printer list.
|
|
|
|
| |
Make the about dialog a bit less barren.
|
|
|
|
|
| |
GtkWindow is no longer a container, so don't call
gtk_container_add on it.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add template tests that show the complex dialogs before
destroying them. This reveals that we are leaking in
several of them. These leaks don't show up if the
dialogs are destroyed right away, as the existing
tests do.
Disable the two failing tests for now:
/template/GtkFileChooserDialog/show
/template/GtkPrintUnixDialog/show
|
|
|
|
| |
This is purely cosmetic.
|
|
|
|
|
|
|
|
|
|
| |
In the presence of attached children, the css tree and the
widget tree are not in sync, so we need to explicitly set
the parent of the css node before inserting the widget, or
else we end up with critical warnings and a non-working
menu.
This can be seen in testtextview.
|
|
|
|
|
|
|
|
| |
If we use "text" for the children that are attached to the
text view, they end up rendering the same background as the
main text content, causing that content to be covered up.
Fixes: #2729
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Extract GtkWindow dragging and titlebar actions
Closes #2689
See merge request GNOME/gtk!1814
|
| |
| |
| |
| | |
Add the 2 new css nodes.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since GtkWindowHandle and GtkHeaderBar do it now, it can be removed from
GtkWindow, along with GTK_WINDOW_REGION_TITLE which at this point doesn't
differ from GTK_WINDOW_REGION_CONTENT.
Closes https://gitlab.gnome.org/GNOME/gtk/-/issues/2689, since
GtkWindowHandle doesn't do that anymore.
|
| |
| |
| |
| |
| | |
This allows it to continue being draggable when placed inside a window, and
will allow to remove the corresponding gestures from GtkWindow.
|
| |
| |
| |
| | |
This will allow to easily wrap it into another widget in the next commits.
|
| |
| |
| |
| | |
This will allow to move the titlebar handling logic out from GtkWindow.
|
| |
| |
| |
| |
| | |
Right now it assumes that the parent is a GtkWindow. This will break when
window dragging is handled by another widget.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Not a direct dependency, but the freetype package is missing it atm
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
window: Remove some dead code
Closes #2726 and #2724
See merge request GNOME/gtk!1862
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the schema is supported, we want to remove
the error style class, not add it again. Pointed
out by Rafał Mikrut.
Fixes: #2724
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were checking x_offset twice, when we meant to check
x_offset and y_offset. Pointed out by Rafał Mikrut.
Fixes: #2726
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It turns out that we have a ref leak at the very
core of our dom model :( gtk_widget_insert_before/after
leak a reference if the widget was already under
the same parent. This is something that GtkBox
frequently does. It shows up e.g. when packing
widgets at the end in a headerbar.
|
| | |
| | |
| | |
| | |
| | | |
When reordering a widget that is alrady under the
same parent, we must not take another reference.
|
|/ /
| |
| |
| | |
We are not attaching windows anymore.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
clipboard: GdkContentProviderUnion should return after writing the first matched format
See merge request GNOME/gtk!1856
|
| |/
| |
| |
| |
| |
| |
| | |
matched format
It continues trying with the other providers due to a missing early
return.
|
|\ \
| | |
| | |
| | |
| | | |
gsk: Add GskTransform autocleanup definition
See merge request GNOME/gtk!1859
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
csswidgetnode: Don't check for container
See merge request GNOME/gtk!1861
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The conditions to queue and dequeue a CSS validation
are different; while queueing checks if the widget is
a root, dequeueing checks that AND if the widget is
a container.
GtkWindow is not a GtkContainer anymore, and that is
causing validations to be queued, but never dequeued.
Don't require the widget to be a GtkContainer for
dequeuing.
|
|\ \
| |/
|/|
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!1860
|
| |
| |
| |
| |
| |
| | |
Seeing just the bold headings at the bottom of the
popover is confusing, so just hide the entire grid
in this case.
|
|/
|
|
|
|
|
|
|
| |
The leave signal should not take any arguments,
don't pass the GdkDrop. Update the documentation,
fix the emission and update users to match.
This was showing up as crash when dragging files
over the places sidebar.
|
|\
| |
| |
| |
| | |
Fix an inspector crash
See merge request GNOME/gtk!1855
|
|/
|
|
|
|
| |
Fix the listmodel semantics of the controller model,
by making get_item return a reference.
This was broken in 4b9e5304cc.
|
|\
| |
| |
| |
| | |
modelbutton: Unify activation code paths
See merge request GNOME/gtk!1854
|
|/
|
|
|
|
| |
Opening submenus by Enter or Space wasn't working,
because we had different code paths for activation
via keynav and via click. Unify them.
|
|\
| |
| |
| |
| | |
Ebassi/for master
See merge request GNOME/gtk!1853
|
| |
| |
| |
| |
| |
| | |
We switched from returning a list to returning a C array, which means we
need to update the introspection annotation and the documentation to
match the implementation.
|
|/
|
|
|
| |
We moved from returning a list to returning a C array, and this requires
a change in the annotations.
|