| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
cellrendererpixbuf: Use fallback icons with icon-name
Closes #1809
See merge request GNOME/gtk!728
|
|/
|
|
|
|
| |
This gives us a better chance of finding an icon to show.
Closes: #1809
|
|\
| |
| |
| |
| |
| |
| | |
Make picking insensitive widgets work again
Closes #1816 and #51
See merge request GNOME/gtk!727
|
| |
| |
| |
| |
| | |
Rename the can-pick property to can-target,
and redo the pick flags with more descriptive names.
|
| |
| |
| |
| |
| |
| | |
If the widget is not drawable, it probably doesn't have
an allocation, so asking the question does not make much
sense.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Use the new argument to gtk_widget_pick to allow picking
insensitive widgets.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/51
|
| |
| |
| |
| |
| |
| |
| | |
Use the new argument to gtk_widget_pick to allow picking
insensitive widgets.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1816
|
| |
| |
| |
| |
| |
| |
| | |
This will be used to let the inspector and other users
pick insensitive widgets again. For now, update all
callers to pass no flags, preserving the current
behavior.
|
| |
| |
| |
| |
| | |
The way to influence picking is to implement contains,
we no longer use the pick vfunc.
|
| |
| |
| |
| | |
Treat popovers as a special-case for now.
|
| |
| |
| |
| | |
Implement contains on the handle, instead of pick on the paned.
|
| |
| |
| |
| |
| | |
Let GtkGizmo override the contains() implementation.
Update all callers to pass NULL for the contains_func.
|
| |
| |
| |
| |
| | |
Leave out reactiveness considerations here,
pick will handle those.
|
| |
| |
| |
| | |
We have the api for this now.
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
treeview: Make expanders work again
Closes #1814
See merge request GNOME/gtk!725
|
|/
|
|
|
|
|
|
|
| |
These were broken by the crossing event unification.
We are now generating some more crossing events, and
the treeview was not looking closely enough at the
ones it gets.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1814
|
| |
|
|\
| |
| |
| |
| | |
Inspector work
See merge request GNOME/gtk!724
|
| |
| |
| |
| |
| | |
This is a safeguard against possible crashing css
being autoloaded.
|
|/
|
|
|
|
|
|
|
|
| |
When a root is set on a widget, the style context may
already exist. We need to make sure that the style context
has the right display set.
This was showing up as "css spillover" in the inspector.
Closes: #https://gitlab.gnome.org/GNOME/gtk/issues/1817
|
|\
| |
| |
| |
| | |
Inspector fixes
See merge request GNOME/gtk!723
|
| | |
|
| |
| |
| |
| | |
Save and restore the contents of the css editor in a file.
|
| |
| |
| |
| |
| |
| | |
Keep only the software gl setting for GL, and put it together
with the simulate touchscreen setting in a 'misc' box. This
keeps all the 'show' options nicely grouped.
|
| |
| |
| |
| | |
Just a matter of cleanliness.
|
|/
|
|
|
| |
We were stuffing the layout overlay into the updates_overlay
field, leaving the layout_overlay field unused.
|
|
|
|
|
| |
Commit f1d61d55151eab774e6734c9ff51212a9c6cee73 inadvertedly
destroyed indentation in most of gdksurface.c. Fix this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to render focus rectangles on everything. With
the way focus is propagated nowadays, the theme has to selectively
render focus on certain widgets.
At the same time, we always want to render focus for this
theme, so use the focus pseudoclass, not focus(visible).
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1815
|
|
|
|
|
| |
These functions no longer exist and should not be in
the headers anymore.
|
| |
|
| |
|
|
|
|
|
| |
If there are already layout properties in the ui
file, we shouldn't crash, even if --3to4 is given.
|
|
|
|
|
| |
These were leftovers from an earlier conversion
that did not properly strip empty elements.
|
|\
| |
| |
| |
| |
| |
| | |
Make menu activation work again
Closes #1796
See merge request GNOME/gtk!721
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After we stopped untranslatable delivering events, menus stopped
working 'the second time'. After some painful debugging, it appears
that this is caused by the menushell code deliberately grabbing
on the menubar *after* grabbing on the menu, causing events to
be deleivered to the wrong toplevel. This did not use to matter,
but now we drop these events.
Absent a more thorough rewrite of menus, just don't grab on
the menubar. This makes menu activation work again and does not
appear to have ill effects, on either Wayland or X.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1796
|
|\ \
| | |
| | |
| | |
| | | |
ci: Add JUnit report for the test suite
See merge request GNOME/gtk!718
|
| | |
| | |
| | |
| | | |
Bundles can be useful on branches and MRs as an opt-in.
|
| | |
| | |
| | |
| | |
| | |
| | | |
GitLab's CI will bail out at the first failure, which means the
JSON-to-JUnit conversion script won't run unless it's part of the same
script that we run for building an testing.
|