| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
It was unused through all of GTK 3, so it is not worth supporting.
The best Windows themes do not make use of it at all.
|
|
|
|
| |
This was relying on setting has-focus for initial focus.
|
|
|
|
| |
The changes here are all related to initial focus.
|
|
|
|
|
|
|
|
|
| |
Check that we get the expected sequences of focus
change events for the nonlinear, inferior and ancestor
cases.
It would be nice to do the same checks for crossing
events, but we have no gtk_window_set_hover().
|
|
|
|
|
|
| |
Do runtime checks for the GLib version,
instead of compiling out tests.
This avoids compiler warnings.
|
|
|
|
|
| |
This commit adds gsk_transform_perspective(), gtk_snapshot_perspective()
and support for perspective() in the CSS syntax.
|
|
|
|
|
|
|
|
|
|
|
| |
Make the API expect a tranform of the proper category instead of
doing the check ourselves and returning TRUE/FALSE.
The benefit is that the mai use case is switch (transform->category)
statements and in those we know the category and don't need to check
TRUE/FALSE.
Using the wrong matrix will now cause a g_warning().
|
|
|
|
|
|
| |
And use it.
And test it.
|
|
|
|
|
|
|
| |
In particular, check that to_matrix() and to_2d(), to_affine() and
to_translate() return the same values.
This also requires a recent Graphene version or the tests will fail.
|
|
|
|
| |
This is an attempt to push GskTransform deeper into the stack.
|
|
|
|
| |
Avoid duplicating GtkEditable APIs. Port existing users.
|
|
|
|
| |
We don't have that signal anymore.
|
|
|
|
|
| |
Much better error message than just the one from the node != NULL
assertion in the next line.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Notebook child metas
See merge request GNOME/gtk!594
|
| |
| |
| |
| | |
The pages property must be skipped.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Notebooks have changed.
|
| |
| |
| |
| | |
Flat is gone.
|
|/
|
|
|
| |
It is unfortunate that Visual Studio is unlikely to support VLA usage,
so replace it with g_newa().
|
| |
|
|
|
|
| |
GtkText makes an appearance in many places now.
|
|
|
|
| |
Thats where the focus is nowadays.
|
|
|
|
| |
It gets created on-demand, so isn't NULL.
|
|
|
|
| |
The entries have changed. Reflect that.
|
|
|
|
|
| |
This changed as part of the recent cleanup that removed
some internal boxing.
|
|\
| |
| |
| |
| | |
Assistant cleanup
See merge request GNOME/gtk!581
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Make items-changed never emit 2 signals, instead, always emit only one,
potentially by extending the range reported in items-changed.
And be a lot more exhaustive about autoselect tests.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Do not make position an inout variable
The function is meant to return a range for a given position, not modify
a position. So it makes no conceptual sense to use an inout variable.
2. Pass the selected state as an out variable
Using a boolean return value - in particular in an interface full of
boolean return values - makes the return value intuitively feel like a
success/failure return. Using an out variable clarifies the usage.
3. Allow passing every position value
Define what happens when position >= list.n_items
4. Clarify the docs about how this function should behave
In particular, mention the case from point (3)
5. Add more tests
Again, (3) needs testing.
|
|
|
|
|
|
|
| |
Ironically, these properties are too good - they always
give you a proper value, which is unfortunately different
from the declared default value, which is NULL. So, don't
check these.
|
|
|
|
|
| |
Drop icons that are only used by demos, and check for ones
that are actually used in gtk.
|
|
|
|
| |
This was missing from the list.
|
|
|
|
|
|
| |
I'm coming to the conclusion that the ci test
failures are due to a recently fixed bug in
GListStore.
|
| |
|
|
|
|
| |
Trying to get to the bottom of a ci failure
|
| |
|
|
|
|
|
| |
The buttons in the stack switcher are now toggle buttons, no
longer radio buttons. Update expected output for that.
|
|
|
|
|
| |
The selected property of GtkSingleSelection is not
freely settable, so omit it from notification tests.
|
| |
|
|\
| |
| |
| |
| | |
tests: Bulk add recent items in an idle
See merge request GNOME/gtk!568
|
| |
| |
| |
| |
| |
| | |
Instead of adding them and waiting for the changed signal to be emitted
in the main loop, there might be a race where the change signal is
emitted before we have a chance of spinning the loop.
|
| |
| |
| |
| | |
This changed with box packing changes.
|
| |
| |
| |
| |
| | |
There was a change in internal dialog structure that
is reflected in this output.
|
| |
| |
| |
| | |
The conversion was done with gtk-builder-tool simplify --3to4.
|
| |
| |
| |
| | |
The conversion was done with gtk-builder-tool simplify --3to4.
|
|/
|
|
| |
We can't change positions without a stack.
|
|
|
|
|
| |
We can't quite get rid of its use in the inspector,
but we can make it private.
|