| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Menus are going away.
|
| |
|
|
|
|
|
|
|
|
|
| |
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 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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Don't allow manual creation of popover menus
anymore. This lets us also make GtkModelButton
private
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
contains-focus now returns TRUE when is-focus is TRUE instead of FALSE.
Fixes #2184
|
|
|
|
| |
...and use them.
|
| |
|
| |
|
|
|
|
|
|
|
| |
infobars being a GtkBox doesn't make sense.
Also implement infobars without exposing internal children.
Closes #1957 because it adds the bottom border.
|
|
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/gtk/issues/2080
|
|
|
|
|
| |
Until we can depend on pango 1.44, these will
fail in ci. Partially reverts f1c7803f800588e
|
|
|
|
|
| |
Support allow-breaks and show attributes.
These will be in pango 1.44
|
|
|
|
| |
Lowercase versions work just as well and are much more readable.
|
|\
| |
| |
| |
| |
| |
| | |
Add constraint-based layout manager
Closes #1090
See merge request GNOME/gtk!973
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of playing games with mapping negative symbolic values to
positive ones, let's use the appropriate constants everywhere. This
allows us to use:
GTK_CONSTRAINT_STRENGTH_WEAK * 2
Or
GTK_CONSTRAINT_STRENGTH_STRONG + 1
In code using the public API.
We also store the strength values as integers, so we can compare them
properly, and only turn them into doubles when they are inserted into
the solver, just like every other variable.
|
| |
| |
| |
| |
| |
| |
| | |
Make the 'repeat edit' test make more than to
suggestions in a single edit phase. It turns out
that this does not work, whereas just doing
two in a row does.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
GtkConstraintSolver is an implementation of the Cassowary constraint
solving algorithm:
http://constraints.cs.washington.edu/cassowary/
The Cassowary method allows to incrementally solve a tableau of linear
equations, in the form of:
x = y × coefficient + constant
with different weights, or strengths, applied to each one.
These equations can be used to describe constraints applied to a layout
of UI elements, which allows layout managers using the Cassowary method
to quickly, and efficiently, lay out widgets in complex relations
between themselves and their parent container.
|
|/
|
|
|
|
|
|
| |
The code previously forgot to include the left child of the model's
node. Which of course only happened if that child wasn't NULL, which is
a common case.
Found and test provided by Matthias Clasen.
|
|
|
|
|
| |
This one will be used for comparison
with constraint layouts.
|
|
|
|
| |
Add testcases for spanning children and homogeneity.
|
|
|
|
|
|
| |
Test some obvious conditions. This is mainly
to test the waters for more intesting tests
with other layout managers later.
|
|
|
|
| |
Test that disabled actions aren't activated.
|
|
|
|
|
| |
This one checks for precedence between
class actions and inserted groups.
|
|
|
|
| |
This checks that gtk_widget_query_action works.
|
|
|
|
|
| |
Check that overlapping prefixes are handled
correctly.
|
|
|
|
| |
Check that the class actions are there and work.
|
|
|
|
|
| |
This tests that action group inheritance
behaves as expected.
|
| |
|
|
|
|
|
| |
When we start cycling on a subset, abort
after a while.
|
|
|
|
|
|
|
|
| |
Differentiate between wrapping around and
stopping at the end of the focus chain.
Update the existing tests, and add two
new ones where the difference matters.
|
|
|
|
|
|
|
|
|
|
| |
Add a test that enumerates the focus chain by
emitting move-focus repeatedly, and compares
the result to expected output.
The test expects a ui file and a reference
file as input. The reference file can be created
using the --generate option.
|
| |
|
|
|
|
| |
That is where they belong.
|
|
|
|
|
| |
The menu shell is no longer the direct
parent of menu items.
|
|
|
|
|
| |
The name just made it hard for people to find the
right gesture to use.
|
| |
|
| |
|
|
|
|
|
| |
Replace all uses of gtk_widget_get_surface by
gtk_native_get_surface.
|
| |
|