| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Instead of manually calling gtk_binding_set_activate_event() on an ::event
callback in the save entry.
|
| | |
|
| | |
|
| |
|
|
|
| |
When disconnecting the GtkEntry from the GtkEntryCompletion, we
must remove the controller in order to avoid dangling callbacks.
|
| |
|
|
| |
We can use the already present key controller to handle focus out.
|
| |
|
|
| |
Instead of a ::event signal handler.
|
| |
|
|
|
|
| |
Set up a gesture on the sidebar rows to detect pointer clicks on
it. The row DnD management has been moved to the row widget itself,
it makes more sense even if the drag is began from the sidebar widget.
|
| |
|
|
|
|
| |
Toplevels are about the only widgets interested in these events,
just handle those without going through the capture/bubble handling
code.
|
| |
|
|
|
|
|
| |
We still need a drag gesture both on front (capture) and back (bubble)
to handle dragging from both the GtkWindow widget and chrome in the
headerbar. But we can do it through 2 drag gestures, instead of special
event handling code.
|
| |
|
|
|
| |
We still need to poke the current event at places, but this is
better than the ::event vfunc.
|
| |
|
|
|
|
|
|
|
|
|
| |
This has been broken since we switched key event delivery to follow
the same semantics than pointer/touch. There, GTK+ grabs will influence
the topmost widget during event delivery, rendering the toplevel
unable to handle key navigation. The toplevel must handle those key
events in an explicit manner then.
We don't render the keyboard focus rectangle yet, but I assume that's
something else.
|
| |
|
|
|
| |
Use GtkEventControllerKey and GtkGestureMultiPress to replace key/button
event handling.
|
| |
|
|
|
| |
One less use of ::event in this widget, now mostly left to
map/delete/configure, those puny events.
|
| |
|
|
| |
And drop the ::event vfunc implementation with it.
|
| |
|
|
|
|
|
| |
Use an event controller on GtkFontChooserDialog, a nice side effect
is that we can use gtk_event_controller_key_forward() and
gtk_search_entry_set_key_capture_widget() instead of passing events
around for dialog search.
|
| |
|
|
| |
Use a key controller set up in the UI file instead.
|
| |
|
|
|
| |
Expose the GtkEntry key controller in private API, so we don't have to
create yet another one just to handle focus-out.
|
| |
|
|
|
|
|
|
|
|
| |
Instead of doing all handling manually in the ::event vfunc,
set up drag/multipress gestures on icon images, and implement
emission of ::icon-press/release and DnD there.
As a side effect, the GdkEvent field in ::icon-press/release
signals has been dropped. Callers that might be interested on it
may still use gtk_get_current_event*().
|
| |
|
|
|
|
| |
This isn't really necessary, if keyboard focus forcibly goes somewhere
else we will get ::grab-notify, which is sufficient to deactivate the
button again.
|
| |
|
|
| |
And stop using GtkWidget::event for good.
|
| |
|
|
| |
We were mistakenly assigning an Atom to a flags value.
|
| |
|
|
| |
The cherry-pick missed this, I guess.
|
| |
|
|
|
| |
(A) Use gsize to match the result of g_variant_n_children
(B) Use guint for n_matches, like the struct (and all other n_matches)
|
| |
|
|
|
| |
Now that .linked acts like the .path-bar already did, there is no point
in applying the same styles again (with higher specificity).
|
| |
|
|
|
|
| |
As discussed in !129
Closes !129
|
| |
|
|
| |
This ought to be controlled via css these days.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The icon will have the size given by css, not whatever
GTK_ICON_SIZE_BUTTON was.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
e.g. the box.linked one, which didn't update the compiled CSS.
|
| |
|
|
|
| |
The new rule does not need to affect all those other pseudoclasses. I
just put it in the wrong scope.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Selected rows in tree views in HighContrast have a background colour the
same or nearly as the normal text colour, so we cannot let entries in
such rows have transparent backgrounds, or the text inside the entry
becomes nearly or totally impossible to see.
Dodge this by giving entry.flat inside treeview and with :focus the
$base_color, which is different from the text & so lets that be seen.
https://gitlab.gnome.org/GNOME/gtk/merge_requests/125
|
| |
|
|
| |
https://gitlab.gnome.org/GNOME/gtk/merge_requests/206
|
| |\
| |
| |
| |
| |
| |
| | |
application: Complete the startup sequence before quitting remote instances
Closes #979
See merge request GNOME/gtk!156
|
| | |\
| |/
|/|
| | |
# Conflicts:
# gdk/gdk.c
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This was causing another docs build break.
|
| | |
| |
| |
| | |
Invalid syntax in gdk4-sections.txt was causing docs builds to fail.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "Crash clearing GtkEntry icon tooltip"
Closes #1160
See merge request GNOME/gtk!205
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The else case was wrongly resetting the accessible description on the
primary icon, which might not exist and can therefore cause a crash.
https://gitlab.gnome.org/GNOME/gtk/issues/1160
|
| | | |
| | |
| | |
| | | |
This should fix gtk-doc erroring out.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 8e74eb382f0c617b7b65a6850952d6acc9fd3018.
This code is not necessary. It worked around a bug in graphene where
graphene was requiring stricter alignment than glib allocators could
guarantee.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit c02bc22cc575470aab870599f2781c3781fb75e6.
This code is not necessary.
The bug causing this problem ws prsent in the graphene library.
|
