| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Use the infrastructure already available to look up keys, instead.
This does the right thing and looks up the setting across all
sources.
Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/3680
|
| |\
| |
| |
| |
| | |
Adwaita: control surface for resize tiled windows
See merge request GNOME/gtk!3212
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- window resizing control area is implemented as where the shadows are drawn
- create a 'fake' shadow for the tiled case to allow easier resizing of
the tiled window ratio even if it's offset to the side of the border
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3670
|
| |\ \
| |/
|/|
| |
| | |
imcontextsimple: Bring back modifier intent
See merge request GNOME/gtk!3213
|
| |/
|
|
| |
This was lost by accident in 85d34932f3888caecd4b.
|
| |\
| |
| |
| |
| | |
Adwaita: Avoid fine-tune scrollbars jumping
See merge request GNOME/gtk!3210
|
| |/
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3672
|
| | |
|
| |\
| |
| |
| |
| | |
Adwaita: Scrollbar transitions and size
See merge request GNOME/gtk!3205
|
| | |
| |
| |
| |
| |
| |
| | |
- tone down the size of the controller again
- transition between the indicator and control fluidly
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/1886
|
| |\ \
| |/
|/|
| |
| | |
Add scaling adjustment for touch dragging a scrolled window
See merge request GNOME/gtk!2615
|
| | |
| |
| |
| |
| |
| |
| |
| | |
If a GtkScrollable uses a different scale than pixels the offset from a
drag must be adjusted to match this scale. This fixes issues like this
https://gitlab.gnome.org/GNOME/vte/-/issues/283 where the terminal
widget uses rows instead of pixels as its scale for each GtkAdjustable
thus causing a 1 pixel vertical drag to scroll 1 row.
|
| |\ \
| | |
| | |
| | |
| | | |
Lenient compose parsing 3
See merge request GNOME/gtk!3202
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
X11 allows keysyms to be specified in addition to strings.
We only support the strings. In the past, we ignored everything
after the string. Go back to doing that, but issue a warning
that we've ignored the keysym.
|
| |\ \ \
| |/ /
| | |
| | |
| | | |
imcontext: Fix a regression in Compose file parsing
See merge request GNOME/gtk!3200
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We accidentally dropped the handing of # comments.
Bring it back.
Fixes: #3664
|
| |/ / |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
wayland/window: Add API to overwrite surface frame requests
See merge request GNOME/gtk!3111
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This is useful when clients use subsurfaces independently of GDK.
For example if a client creates a subsurface that covers a GdkWindow
entirely. If this subsurface is opaque, Wayland compositors may not
emit callbacks for the surface of the GdkWindow any more.
Adding the covering subsurface via this new API ensures the
GdkWindow will continue to update in this case.
|
| |\ \
| | |
| | |
| | |
| | | |
Adwaita: Bring back borders of tiled windows
See merge request GNOME/gtk!3185
|
| |/ /
| |
| |
| | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3661
|
| |\ \
| | |
| | |
| | |
| | | |
adwaita: disable shadows when window is maximized, fullscreen, tiled
See merge request GNOME/gtk!3179
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
These shadows cause a significant draw performance drop for maximized
windows. Disabling them increases the chances we can have faster scroll
performance of text.
There is some risk here for systems where they have a dock and you expect
the shadow to draw beneath that dock for transparency reasons.
|
| |\ \
| | |
| | |
| | |
| | | |
Fix imcontext crash
See merge request GNOME/gtk!3174
|
| |/ /
| |
| |
| |
| |
| | |
In the backport, I inadvertendly removed the
set_client_window implementation, which needs
to remain.
|
| |\ \
| | |
| | |
| | |
| | | |
imcontext: Backport compose sequence improvements
See merge request GNOME/gtk!3172
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Improve compose sequence handling:
- Show preedit for compose seqences
- Support sequences of up to 20 code points
- Warn when ignoring Compose file features
- Support compose sequences producing multiple characters
- Support hex escapes
|
| |\ \
| | |
| | |
| | |
| | | |
printing: Create temporary queues for Avahi printers (Gtk 3)
See merge request GNOME/gtk!3161
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit unsubscribes CUPS backend from a DBus
signal in idle when listening for new items on Avahi.
Since GDBus emits gathered signals in idle while
checking whether the signal has been unsubscribed
it could happen that a signal was not processed
because it was removed from hash table of
subscribed signals.
This caused the situation where printers advertised
on Avahi were not listed in CUPS backend sometimes.
We need those signals since this happens when switching
from a general subscription which listens to signals
for all Avahi services to a specific one which listens
to just _ipp._tcp and _ipps._tcp (chicken and egg problem).
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change extends set of Avahi advertised printers which
works with Gtk's CUPS print backend.
It creates a temporary queue (local printer) for each
Avahi printer in CUPS instead of accessing them directly
(via CUPS library).
This makes some printers work which did not work before and
also gives users more options to change in the print dialog.
This also changes naming of printers to be in accordance with CUPS.
It uses '_' instead of '-' and has hostname appended for CUPS remote
printers.
|
| |\ \
| | |
| | |
| | |
| | | |
Meson: Avoid UAC on 32-bit Windows for gtk-update-icon-cache
See merge request GNOME/gtk!3147
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As the program executable name has 'update' in its filename,
gtk-update-icon-cache.exe is considered to be an installer program on 32-bit
Windows [1], which will cause the program to fail to run unless it is running
with elevated privileges (i.e. UAC).
Avoid this situation by embedding a manifest file into the final executable
that tells Windows that this is not a program that requires elevation.
Also make the autotools build files dist the new script and use the new script
to generate the manifest and rc files, instead of hardcoding the generating
bits in gtk/Makefile.am
Fixes issue #3632.
[1]: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc709628(v=ws.10)?redirectedfrom=MSDN,
under section "Installer Detection Technology"
|
| |\ \
| | |
| | |
| | |
| | | |
Support gtk-shell surface release destructor
See merge request GNOME/gtk!2074
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds a "release" destructor for the gtk_surface1 interface which
signals to the server that a surface has been destroyed on the client
side, which the current "destroy" does not do.
Ideally the protocol would have specified a destroy request marked as
destructor to handle this automatically, however this is no longer
possible due to the destroy method being implicitly generated in the
absence of an explicit request in the protocol. Adding a destroy request
marked as destructor now would generate a new destroy method that
unconditionally would send the request to the server, which would break
clients running on servers not supporting that request.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Adds support for Android/Chrome on-screen keyboard
See merge request GNOME/gtk!3130
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Adds event listener for input events; converts input data into
key press and key release commands depending on inputType of the event.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Adwaita: make scrollbars larger
See merge request GNOME/gtk!3110
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When using scrollbars as active controls, rather than their primary role as indicators,
increase their size as click targets.
Fixes https://gitlab.gnome.org/GNOME/gtk/issues/1886
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Allow GTK_DEBUG=interactive even without G_ENABLE_DEBUG defined
See merge request GNOME/gtk!3090
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently when GTK3 is compiled without G_ENABLE_DEBUG, the inspector
can't be opened with GTK_DEBUG=interactive because it doesn't parse
this env var without G_ENABLE_DEBUG.
Since the inspector is always good to have, this commit now always
parses the GTK_DEBUG env var but only keep the "interactive" flag if
G_ENABLE_DEBUG isn't defined.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
gdk/wayland: Mark matched settings from the portal as valid (3.24)
See merge request GNOME/gtk!3077
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Commit e6209de9625 added some checks on TranslationEntry.valid in
order to figure out whether using the new font settings or the
old g-s-d ones. However that's only set in the non-sandboxed case.
This makes sandboxed applications fallback to the old (and also
non-existing with modern g-s-d) settings, possibly resulting in
ugly defaults being picked.
Fix this by also marking TranslationEntry elements as valid when
using the settings portal, precisely those entries that we are able
to read and match with our own table.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Wayland: Fix segfault when receiving tablet/touch events for surfaces that have already been destroyed client-side
See merge request GNOME/gtk!2809
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When destroying a wl_surface (e.g. when a window or menu is closed), the
surface may continue to exist in the compositor slightly longer than on
the client side. In that case, the surface can still receive input
events, which need to be ignored gracefully.
In particular, this prevents segfaulting on wl_surface_get_user_data()
in that situation.
Reported in
https://gitlab.gnome.org/GNOME/gtk/-/issues/3296
The same issue for pointers/keyboards was reported in
https://bugzilla.gnome.org/show_bug.cgi?id=693338
and fixed with in
bfd7137ffbcbd8caa531d7a47d799fefb6605a5a
3625f17857328ae7e7aa43340f29efa56575a7b0
a8fc099a725543649fe3aab76943c14bdcd860fc
|
