| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The condition we check for to catch X servers going away
may not be accurate anymore, and the warning shows up in
logs, causing customers to be concerned. So, be quiet by
default, unless the user explicitly asked for a message.
|
|\
| |
| |
| |
| | |
fontchooser: Fix some since annotations
See merge request GNOME/gtk!3428
|
|/
|
|
|
|
|
| |
The "level", "font-features" and "language" were annotated
with the wrong version.
Fixes: #1830
|
|\
| |
| |
| |
| | |
docs: Remove any reference to GtkGrid in Gtk[HV]Box
See merge request GNOME/gtk!3422
|
| |
| |
| |
| |
| |
| |
| |
| | |
GtkBox is not going away, so there's not point in making things more
confusing for those who are still porting their code from GTK2 to GTK3
10 years after GTK 3.0 was released.
Fixes: #3854
|
|\ \
| |/
|/|
| |
| | |
scale: Fix sporadic criticals
See merge request GNOME/gtk!3421
|
|/
|
|
|
|
|
| |
gtk_css_node_update_layout_attributes can cause us to
free priv->layout, and then bad things happen. Therefore,
we must call that function on a new layout *before* setting
priv->layout.
|
|\
| |
| |
| |
| | |
Fix typo on gtklistbox.c's docs
See merge request GNOME/gtk!3418
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
wayland: Improve font setting fallback more
See merge request GNOME/gtk!3409
|
|/
|
|
|
|
|
|
| |
We may get a response from the portal that contains
no useful settings at all. In that case, we should
fallback as well.
Fixes: #3838
|
|\
| |
| |
| |
| | |
wayland: Improve font setting fallback
See merge request GNOME/gtk!3406
|
|/
|
|
|
|
|
| |
When we don't get stettings from the portal, the current
fallback is 'awful fonts'. There is no need for that. Instead,
set the fallback values to grayscale antialiasing with slight
hinting.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Revert Compose sequence changes
See merge request GNOME/gtk!3387
|
|/
|
|
|
|
|
|
|
|
|
| |
This was breaking muscle memory of people with
the us intl keyboard layout, for important keys
such as '. The unfortunate side-effect is that
our handling of <dead_acute> is a bit hampered
by sequences that don't fit the pattern. But
such is life.
Fixes: #3807
|
|\
| |
| |
| |
| | |
scrolledwindow: Cancel overshoot on dimension changes
See merge request GNOME/gtk!3333
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we scroll down in a list that's still being filled, we hit the edge and
initiate overshoot, and then the adjustment's upper value increases. This
leads to an unwanted bounce back.
Additionally, if in a similar situation the upper value decreases, the
overscroll glow gets stuck.
Update kinetic scrolling upper and lower value on changes, and immediately
cancel it if dimensions on that side change.
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3752
|
|\ \
| | |
| | |
| | |
| | | |
gdk/wayland: Defer processing of globals closures
See merge request GNOME/gtk!3357
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
... until all globals have been received.
The dependency tracking introduced in 4e9be39518 only allows to
specify required globals and processes the closures as soon as
the requirements have been met. There are, however, also optional
dependencies - most notably the primary_selection protocol.
Currently we rely on the fact that compositors like Mutter announce
it before `wl_seat`, even though the order is not specified in
the spec.
Process globals closures only after all globals have been announced,
so optional dependencies can be accommodated.
Closes https://gitlab.gnome.org/GNOME/gtk/-/issues/3791
|
|\ \
| | |
| | |
| | |
| | | |
spinbutton: Interpret localized digits
See merge request GNOME/gtk!3369
|
| | |
| | |
| | |
| | |
| | |
| | | |
Interpret input where the characters have numeric values.
See #3387
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
label: Fix reacting to screen resolution changes
See merge request GNOME/gtk!3368
|
|/ /
| |
| |
| |
| | |
Labels were not reacting when the screen resolution
changes, as e.g. when turning "Large Text" on of off.
|
| |
| |
| |
| |
| |
| |
| | |
The documentation states that GTK will load a Compose
file from ~/.config/gtk-3.0/Compose. Unfortunately,
backports changed this unintentionally to look in
the gtk-4.0 directory. Change it back.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
GDK quartz: Keep window without decoration miniaturizable
See merge request GNOME/gtk!3281
|
| | |
| | |
| | |
| | | |
Closes #2345
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Double dead keys 3
See merge request GNOME/gtk!3354
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Reshuffle things to allow for a limited amount of
dead key 'chaining'. We keep up to 2 dead keys in
the preedit, so you can type
<dead_acute> <dead_cedilla> <c>
to produce ḉ, while still getting ```c with
<dead_grave> <dead_grave> <dead_grave> <c>.
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Only check for combinations of up to 2 dead keys with
a base character. We don't want to spend ages generating
all permutations of long sequences.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
cssshadowvalue: Apply device scale to the offset when blurring text
See merge request GNOME/gtk!3343
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Although the surface already has the device scale set, that doesn't
apply to the offset which is in raw device units. So we need to scale
the device offset explicitly.
Fixes: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/119
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
[gtk3] x11/dnd: Ignore XErrors from the COW
See merge request GNOME/gtk!3335
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The DnD code for X11 adds the composite overlay window (aka COW) to the
cache.
Yet the X11 requests to get and release the COW may trigger XErrors that
we ought to ignore otherwise the client will abort.
Fixes: #3715
|
|\ \
| | |
| | |
| | |
| | | |
Better dead keys 3
See merge request GNOME/gtk!3330
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update our compose sequences based on the current
update xorg Compose.pre file. Beyond that, remove
some deadkey sequences that we are now handling
(better) in code.
|
| | |
| | |
| | |
| | | |
This reduces the clutter in gtk/.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make this script parse gtk-compose-remove.txt for
sequences to remove from the xorg Compose file.
This will be used for removing some deadkey combinations
that we can handle better in code.
Also, make this script explicitly python2. I tried
porting it to python3, but gave up in the end.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For sequences like ``, we want to commit the first
deadkey and then continue preedit with the second.
The alternative is to do chained deadkeys, where
entering ~~a yields ̃̀̃̃a. But we don't do that, and
I think that would be more controversial.
|
|/ /
| |
| |
| |
| |
| | |
For sequences like `x, where we don't have a compose
sequence, we still want to commit "`x", and not silently
eat the keys.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
wayland: Pass layout information in key events
See merge request GNOME/gtk!3302
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were always setting group to 0, causing accelerator
interpretation to always go off the first configured
layout, not the active one.
Fixes: #1825
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Reproducible icon cache
See merge request GNOME/gtk!3293
|