| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
- they don' exist, but they can look good
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3369
|
|\
| |
| |
| |
| |
| |
| | |
Wip/jimmac/menu clipped shadow
Closes #1987
See merge request GNOME/gtk!2837
|
| |
| |
| |
| | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/1987
|
|/
|
|
|
|
| |
- clipping a rounded corner seems to be working fine for first and last item.
Addresses https://gitlab.gnome.org/GNOME/gtk/-/issues/3366
|
|\
| |
| |
| |
| |
| |
| | |
Adwaita: navigation sidebar color changes
Closes #3362
See merge request GNOME/gtk!2836
|
| |
| |
| |
| |
| |
| | |
- use more subtle selected state grey
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3362
|
|\ \
| | |
| | |
| | |
| | | |
Matthiasc/for master
See merge request GNOME/gtk!2835
|
| | |
| | |
| | |
| | | |
The Characters demo was leaking its columns.
|
|/ /
| |
| |
| |
| |
| |
| | |
The expected behavior when activating check or radio
menuitems via keynav is that Space toggles the item
but keeps the menu open, while Return toggles the
item and closes the menu.
|
|\ \
| | |
| | |
| | |
| | | |
Fix tooltip triggering
See merge request GNOME/gtk!2833
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ever since 5b5d2665d373c35f, tooltips don't work properly,
since we get more motion events now, and those keep the
tooltips from appearing. This can be seen e.g. on the icon
in the password entry in widget-factory, or on the section
switcher buttons in the Emoji chooser.
Ignore synthetic motion events for the purposes of
determining whether the user moved the mouse.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
gtkwidget: fix crashes with GTK_A11Y=none
Closes #3333
See merge request GNOME/gtk!2834
|
|/ /
| |
| |
| |
| |
| | |
at_context can be NULL in that case, so guard against it.
Fixes #3333
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Adwaita: Stop using $button_fill
Closes #3354
See merge request GNOME/gtk!2828
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since the $button_fill variables are no longer used outside of the
button() mixin (and it was for an ugly hack), there is no need to keep
that anymore.
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3354
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Always parse GTK/GDK/GSK_DEBUG env vars and make some entries available in non-debug mode
See merge request GNOME/gtk!2830
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
non-debug mode
Currently GTK can be built with G_ENABLE_DEBUG which enables various debug code and parsing
of those env vars, or without, which instead of parsing them prints a warning if they are set.
While building with G_ENABLE_DEBUG isn't strictly needed it's the only way to make GTK_DEBUG=interactive work,
which is a nice thing to have always.
This enables parsing of those env vars in any case and allows specific values being marked as also
available when not built with G_ENABLE_DEBUG (interactive for example). If not built with G_ENABLE_DEBUG
then all unavailable values will be marked as such in the help output and a note is added that
GTK needs to be built with G_ENABLE_DEBUG to use them, which should help discoverability.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
gtk_tree_model_iter_next to state that the ITER parameter is modified."
This reverts commit 1340ff2bc279329dc16b8d823100fec46b2f11d8.
Same as with 53cd499621b5
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
gtk/main: Reset active state on grab broken only if implicit
See merge request GNOME/gtk!2832
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
An implicit grab means some button is down, reset the active state
only in that case when we get a grab broken event.
Avoids active state accounting warnings when we do get active grabs
broken (e.g. after selecting a menu option).
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Matthiasc/for master
Closes #3359 and #3353
See merge request GNOME/gtk!2827
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit bfe5b0d1b7a1374964 ran into some specificity
trouble.
Fixes: #3353
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit 0db504edde63eb77e made a mistake described here:
https://en.wikipedia.org/wiki/Short-circuit_evaluation#Possible_problems
Fixes: #3359
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
ci: publish demo apps to the Nightly repository
See merge request GNOME/gtk!2825
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Adwaita: tooltip styling
Closes #3352
See merge request GNOME/gtk!2826
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
- balance padding
- increase border radius, yuck
- get rid of text shadow
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3352
|
|\ \
| | |
| | |
| | |
| | | |
Wip/jimmac/submenus
See merge request GNOME/gtk!2824
|
| | |
| | |
| | |
| | |
| | |
| | | |
- all corners have rounded corners
See https://gitlab.gnome.org/GNOME/gtk/-/issues/2745
|
| | |
| | |
| | |
| | | |
- this was already in place in _common, no need to have it in _colors
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Adwaita: double declated $button_fill
See merge request GNOME/gtk!2823
|
|/ /
| |
| |
| | |
- this was already in place in _common, no need to have it in _colors
|
|\ \
| |/
|/|
| |
| | |
Round window corners
See merge request GNOME/gtk!1952
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Improve handling of ::active with touch and multiple foci
Closes #3348
See merge request GNOME/gtk!2821
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We may have the situation of multiple touchpoints in the same
widget, or combinations with other devices. Stack those ::active
states are preserved on widgets on all but the last pointer/touch
going away.
|
|/ /
| |
| |
| |
| |
| |
| | |
This went missing at some point, add the missing toggling of active
state with GDK_TOUCH_BEGIN/END/CANCEL events.
Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/3348
|
|\ \
| | |
| | |
| | |
| | | |
Ebassi/for master
See merge request GNOME/gtk!2819
|
| | |
| | |
| | |
| | | |
And hide the image from the accessible tree.
|
| | |
| | |
| | |
| | | |
We reuse the existing implementation in GTK3.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Use the GROUP role, and make sure to note that the child is always
revealed. Unlike GtkExpander, GtkRevealer can only be programmatically
toggled, so we cannot turn it into a "button" object.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Document the role of the GtkTreeExpander, and the behaviour of the
expander button.
Additionally, improve the label of the expander button, by adding a
fixed "Expand" label, and setting the "labelled-by" relation to the
child of the GtkTreeExpander.
|
| | |
| | |
| | |
| | |
| | | |
The search entry changes the content of the list view, so we should
mention that relation to assistive technologies.
|
| | |
| | |
| | |
| | |
| | | |
Just like GtkPasswordEntry, GtkSearchEntry should have its set of
accessible actions.
|
| | |
| | |
| | |
| | |
| | | |
While the "clear the search entry" icon behaves like a button, we don't
have any actual action that can trigger it, so let's ignore it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The search bar widget has a "SEARCH" landmark role, which is described
as:
A landmark region that contains a collection of items and
objects that, as a whole, combine to create a search facility.
|
| | |
| | |
| | |
| | | |
Buttons are described by text, and the icon child can be safely ignored.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Label the various components:
- the tab list
- the tab widget
- the arrow widgets
|