| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Call it gtk_window_set_default_widget, to match
the getter, and the property name. Update all
callers.
|
|
|
|
| |
This is a part of redoing default widget handling.
|
|
|
|
|
|
| |
Since actions are used increasingly, we should
have a convenient way to trigger an action in
the context of a widget.
|
|\
| |
| |
| |
| | |
Focus cleanup
See merge request GNOME/gtk!788
|
| |
| |
| |
| | |
These critical warnings break the tests, otherwise.
|
| |
| |
| |
| |
| |
| |
| | |
This api wasn't used anywhere in GTK. And since
we've dropped the variant for the default widget,
this one should go too. If it is needed, it should
become and action too.
|
| |
| |
| |
| |
| |
| |
| | |
We used to handle has-focus in ui files specially.
It was awkward, so stop doing that. If you need
to influence the initial focus of a window, you
can just set the focus-widget property.
|
| |
| |
| |
| |
| |
| | |
We were assuming that the parent class has a custom
set_property, which may not be the case. Be more
careful.
|
|\ \
| |/
|/|
| |
| | |
inspector: Make property list sortable again
See merge request GNOME/gtk!787
|
|/
|
|
|
|
| |
We lost this when moving from a treeview to
a listbox. Bring it back, with homegrown list
headers.
|
|\
| |
| |
| |
| |
| |
| | |
file chooser: Stay focused
Closes #1851
See merge request GNOME/gtk!785
|
|/
|
|
|
|
|
|
|
|
|
| |
When hitting Escape in the location entry,
we were not moving the focus anywhere,
causing focus to be NULL, and key bindings
to stop working. The visible effect was
that Ctrl-L / Escape / Ctrl-L would not
get back to the location entry, as expected.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1851
|
|\
| |
| |
| |
| | |
Assorted filechooser improvements
See merge request GNOME/gtk!783
|
| |
| |
| |
| |
| | |
This way we can avoid a slight position offset when we show or hide the
spinner during a search.
|
| | |
|
| |
| |
| |
| | |
We generally do that for all properties.
|
| |
| |
| |
| |
| | |
This doesn't really make sense, we can assume that the treeview already
has the focus when it receives key events.
|
| | |
|
| |
| |
| |
| | |
It's just weird that the search entry does not have focus while we type.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Add some space between the icons and the text, like there was in gtk3.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
file chooser: Prevent accidental search
Closes #1850
See merge request GNOME/gtk!784
|
|/
|
|
|
|
|
|
|
|
| |
When hitting Escape, the file chooser will go
into search mode, because the search entry
consumes the key to emit the ::search-stopped
signal. Recognize this situation and avoid
switching to search mode in this case.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1850
|
|
|
|
|
|
|
| |
The primary icon is on the right in RTL, so don't offset the text child
to the right for it.
Fixes the text and icon overlapping in the second entry
in tests/testentryicons
|
| |
|
|
|
|
|
|
| |
It doesn't make sense to keep track of all the last_* values anymore now
that widgets only get allocated when their size changes anyway.
Remove all the associated (and thus now unused) flags as well.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Popover demos
See merge request GNOME/gtk!782
|
| |
| |
| |
| |
| | |
Add an expander to a popover to test how
changing sizes works with popovers.
|
| |
| |
| |
| |
| | |
These are mainly for stress-testing our
popover implementations.
|
| |
| |
| |
| |
| |
| | |
This makes is easy to test moving the toplevel
or repositioning the parent while the popover
is shown.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
file chooser: Fix Ctrl-L
Closes #1829
See merge request GNOME/gtk!781
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We were forwarding key events to the search entry
and unconditionally considered search started
afterwards. That is not correct, since things
like a Ctrl key press should not trigger search.
Fix this by only switching to search mode when
the event was actually consumed.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1829
|
|\ \
| |/
|/|
| |
| |
| |
| | |
fontchooser: Fix type-to-search
Closes #1842
See merge request GNOME/gtk!780
|
|/
|
|
|
|
|
|
|
| |
The key capture was interfering with other
entries in the dialog, so be smarter about
when we want to capture keys and when we
don't.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1842
|
|
|
|
|
|
|
|
|
| |
Just measuring it (so the warning goes away) but then not using the
values will later underallocate the text widget.
Instead, always reserve space for the icon (which will inevitable be
visible as soon as the searchentry is actually being used).
Fixes #1831
|
|
|
|
|
| |
The first rule breaks GtkText inside GtkSearchEntry inside something
that has .view applied, as found in the file chooser when searching.
|
|
|
|
| |
... instead of g_spawn(). Avoids having to create a temp file, too.
|
|
|
|
|
|
| |
When rendering to a texture, collecting the render ops might bind a
different framebuffer, so bind the one we want again before doing the
actual rendering.
|
|
|
|
|
| |
Otherwise the coordinates passed to the query-tooltip signal are always
0.
|
|\
| |
| |
| |
| | |
Surface transform listener fixes
See merge request GNOME/gtk!776
|
| |
| |
| |
| |
| | |
The purpose being to reduce the size of GtkWidgetPrivate. What is left
is a pointer to the allocated struct.
|
| |
| |
| |
| |
| | |
It was never added, as the listener was replaced by explicit code in
gtk_widget_(un)root(), but the removal code was left in place in error.
|
|\ \
| | |
| | |
| | |
| | | |
gdksurface-win32.c: Acquire root coordinates on drag/move
See merge request GNOME/gtk!693
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As in commit d45996c, the x and y coordinates passed into begin_drag and
begin_move are no longer root coordinates but are now surface
coordinates.
Use the x and y surface coordinates to acquire the root x and y
coordinates so that resizing and moving can work as expected.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Add GL debugging integration
See merge request GNOME/gtk!771
|