| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Some css parser tests were relying on the parser preserving
some units. Update them. The numbers look uglier this way,
but they are the same numbers the css machinery was using
anyway.
|
|
|
|
| |
We now print colors differently in some places.
|
| |
|
| |
|
| |
|
|
|
|
| |
Menus are going away.
|
| |
|
|
|
|
| |
Some of the expected output needs to be updated.
|
|
|
|
|
|
|
|
|
| |
When looking for the get_type function for GThemedIcon,
try both g_themed_icon_get_type and gthemed_icon_get_type
The former is what gio has, the latter is still supported
to avoid breaking gweather_location_get_type.
Update tests to cover this new case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkBuilderScope is an interface that provides the scope that a builder
instance operates in.
It creates closures and resolves types. Language bindings are meant to
use this interface to customize the behavior of builder files, in
particular when instantiating templates.
A default implementation for C is provided via GtkBuilderCScope (to keep
with the awkward naming that glib uses for closures). It is derivable on
purpose so that languages or extensions that extend C can use it.
The reftest code in fact does derive GtkBuilderCScope for its own scope
implementation that implements looking up symbols in modules.
gtk-widget-factory was updated to use the new GtkBuilderCScope to add
its custom callback symbols.
So it does it different from gtk-demo, which uses the normal way of
exporting symbols for dlsym() and thereby makes the 2 demos test the 2
ways GtkBuilder uses for looking up symbols.
|
|
|
|
|
|
| |
They were failing to return a reference where they
need to. This was uncovered by fixing an unrelated
ref leak.
|
|
|
|
|
|
|
|
| |
All the list model tests were leaking items,
because g_list_model_get_item is transfer full.
Fixing these unveils a crash in the treelistmodel
and maplistmodel tests.
|
|
|
|
|
|
|
|
| |
We weren't correctly ending the ( ) block when encountering an error.
Testcases added.
Fixes #2281
|
| |
|
|
|
|
| |
All tools got renamed to have a gtk4 prefix.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Adwaita: Avoid directly coloring labels wherever possible (GTK4)
Closes #1643
See merge request GNOME/gtk!1209
|
| |
| |
| |
| |
| | |
Properly unset theme CSS and use the right selector for the toggle
buttons.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use a compilation symbol in our build to allow the inclusion of
specific headers while building GTK, to avoid the need to include only
the global header.
Each namespace has its own compilation symbol because we used to have
different libraries, and strict symbol visibility between libraries;
now that we have a single library, and we can use private symbols across
namespaces while building GTK, we should have a single compilation
symbol, and simplify the build rules.
|
|/ |
|
|
|
|
| |
This reverts part of 91497348bf1ea90ef1056bdc8727bbea645c21e3
|
|
|
|
|
|
|
| |
This change was lost during the parser changes, but the newly added test
exposes it.
And fix the expected error, the syntax has changed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bug was introduced in commit:
9b7640b8 by Benjamin Otte, 2012-03-26 17:24:02
styleproperty: Make _gtk_style_property_parse_value() return a CssValue
In that commit, `values` changed from `GValue*` to `GtkCssValue**`,
but one `!G_IS_VALUE (&values[8])` was left untouched. As a result,
if `border` shorthand contains anything after color, it might crash,
depending on memory layout.
New test included.
Fixes: #751
|
|
|
|
|
|
| |
gtk_builder_connect_signals() is no longer necessary, because all the
setup that made it necessary to have this extra step is now done
automatically via the closure functions.
|
| |
|
|
|
|
|
|
|
|
| |
This is pretty unused and gets in the way of the next steps.
A potential side effect is that for templates the widget was passed as
the user data argument. If that turns out to be important, we have to
special case that situation.
|
|
|
|
| |
... and don't instantly abort, test the rest of the properties, too.
|
| |
|
|\
| |
| |
| |
| | |
Privatize popover menu pieces
See merge request GNOME/gtk!925
|
| |
| |
| |
| |
| |
| | |
Don't allow manual creation of popover menus
anymore. This lets us also make GtkModelButton
private
|
|/
|
|
|
|
|
| |
Instead, use the standard library().
This is a meson best practice.
Fixes -Ddefault_library=static not having any effect.
|
|
|
|
|
|
|
|
|
| |
This adds support using the GtkTextHistory helper for undo/redo to the
GtkText widget. It is similar in use to GtkTextView, but with a simplified
interface.
You can disable undo support using the GtkText:enable-undo property. By
default, it is enabled.
|
|
|
|
| |
Changes in Pango may make this test fail.
|
|
|
|
| |
When module loading fails, print out the error.
|
|
|
|
| |
We are not using libtool anymore.
|
|
|
|
|
| |
The tests suite calls `diff` in various places, which means we need to
check if it's installed.
|
|
|
|
| |
Allows not to have anything selected.
|
|
|
|
|
|
|
| |
1. Make the model property construct-only. Allowing to change the
model has invalid side effects.
2. Add a getter for the model property.
|
|
|
|
|
|
|
|
|
|
| |
The expander icon is renamed from "arrow" to "expander".
The expander widget itself is renamed from "expander" to
"expander-widget" (Better ideas welcome).
This makes it possible to have an "expander" icon in more places then
the GtkExpander widget (in particular in tree lists) and not
confuse it with arrows.
|
|
|
|
|
|
| |
contains-focus now returns TRUE when is-focus is TRUE instead of FALSE.
Fixes #2184
|
|
|
|
| |
...and use them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This creates a new GtkTextViewChild that can manage overlay children at
given x,y offsets in buffer coordinates. This simplifies GtkTextView by
extracting this from GtkTextWindow as well as providing a real widget for
the borders.
With this change, we also rename gtk_text_view_add_child_in_window() to
gtk_text_view_add_overlay(). For those that were using
GTK_TEXT_WINDOW_WIDGET, they can use a GtkOverlay. It does not appear
that anyone was using GTK_TEXT_WINDOW_(LEFT|RIGHT|TOP|BOTTOM) for widgets
in this fashion, but that can be done by setting a gutter widget with
gtk_text_view_set_gutter(). We can make GtkTextViewChild public if
necessary to simplify this should it become necessary.
GtkTextViewChild will setup a CSS node of either "text" or "border"
depending on the GtkTextWindowType.
The old GtkTextViewChild has been renamed to AnchoredChild as it is only
used for widgets with anchors in the GtkTextBuffer. This also removes the
use of allocated GSList and instead embeds a GQueue and GList to save a
few extraneous allocations.
|
|
|
|
| |
And incidentally make the CSS node docs correct again.
|
| |
|
| |
|
|
|
|
|
|
|
| |
infobars being a GtkBox doesn't make sense.
Also implement infobars without exposing internal children.
Closes #1957 because it adds the bottom border.
|
|
|
|
| |
It's a full transform and not just a translation these days.
|
| |
|
|
|
|
|
|
| |
Crash pointed out by Bastien Nocera.
Testcase included.
|
| |
|