| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This code is very similar to the handling for these
targets in the clipboard case.
Fixes: #3642
|
| |\
| |
| |
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!3150
|
| | |
| |
| |
| | |
Thats the cleaner way to test internal apis.
|
| |/
|
|
|
| |
Just a few cases for now, enough to test a recently
fixed regression with shadow transitions.
|
| |\
| |
| |
| |
| |
| |
| | |
gtk4-update-icon-cache: Avoid UAC on 32-bit Windows
Closes #3632
See merge request GNOME/gtk!3141
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As the program executable name has 'update' in its filename,
gtk4-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.
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"
|
| |\ \
| | |
| | |
| | |
| | | |
css: Allow transitioning different-size shadows
See merge request GNOME/gtk!3145
|
| |/ /
| |
| |
| |
| | |
The code handles it just fine. The length check was
an erronous addition.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Some im context work
Closes #1004, #186, and #3521
See merge request GNOME/gtk!3143
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a small omission from the Compose file
syntax that doesn't cost us much to support.
Add a test for this syntax too.
Fixes: #1004
|
| | | |
| | |
| | |
| | |
| | | |
Add a test that checks we parse values with
multiple characters correctly.
|
| | | |
| | |
| | |
| | |
| | | |
Change the cache format to include the character
data that we need to hold string values in the table.
|
| | | |
| | |
| | |
| | |
| | | |
This just doesn't make sense. This will use malloc
anyway, so just call malloc directly.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Keep string values in the table, and return them
from the check function. This commit temporarily
disables the table caching, since the cache format
does not handle string values yet.
Fixes: #186
|
| | | |
| | |
| | |
| | |
| | | |
Rewrite the value parsing function to accept strings
that hold more than a single Unicode character.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change the parser data structures to hold a string, rather
than a gunichar. We still only put a single Unicode character
into it, currently.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make it possible for gtk_compose_table_check to return
a string instead of just a single Unicode character.
Currently, we only ever return strings holding a single
character, still.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Reshuffle things so we can easily handle values
that are strings instead of just single Unicode
characters.
|
| | | |
| | |
| | |
| | |
| | | |
Just some spot checks, enough to verify the
fix in the previous commit.
|
| | | |
| | |
| | |
| | |
| | | |
The code wasn't paying attention to (lack of) nul-termination
in one place, causing it to not match when it should.
|
| | | |
| | |
| | |
| | | |
Not very exhaustive, just some spot checks.
|
| | | |
| | |
| | |
| | | |
Get rid of auxiliary check_table function.
|
| | | |
| | |
| | |
| | |
| | | |
Move all the checking code to gtkcomposetable.c, and
add api that we can use in tests.
|
| | | |
| | |
| | |
| | |
| | | |
This tests the api we use to match key sequences
against compose tables.
|
| | | |
| | |
| | |
| | | |
Use the just-introduced api.
|
| | | |
| | |
| | |
| | |
| | | |
This copies the check_table code from gtkimcontextsimple.c,
in order to have an api for tests.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Add some tests for the code that parses Compose files.
This tests the fix in the previous commit.
|
| | | |
| | |
| | |
| | | |
This is better off in the tests that we are going to add.
|
| | | |
| | |
| | |
| | | |
We were not handling octal escapes right.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Drop GTK_MAX_COMPOSE_LEN from docs. It is no longer
used by GTK at all. We leave the define in place
for now, to avoid breaking 3rd party code that might
use it.
|
| | | |
| | |
| | |
| | |
| | | |
We should at least give a hint that we've seen the line,
otherwise people will wonder why nothing happened.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Allow compose sequences of up to 20 code points.
Fixes: #3521
|
| | | |
| | |
| | |
| | |
| | | |
Fix an off-by-one in the code parsing octal escapes
in compose files.
|
| | | |
| | |
| | |
| | |
| | | |
Allocate the compose_buffer, and resize it when needed
to match the tables we use.
|
| | |/
| |
| |
| |
| | |
Use g_clear_pointer instead of opencoding it in
multiple places.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
gdk/toplevelsize: Remove warnings about exceeding bounds
Closes #3035
See merge request GNOME/gtk!3142
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Sometimes the size will exceed the minimum bounds. For example crazy
applications like the widget factory that contains the world, or when a
user interactively resizes a window to be larger than the monitor the
window is on is.
The former is questionable, but the latter is not, and from here we
can't really see the difference, so just stop complaining.
Closes: https://gitlab.gnome.org/GNOME/gtk/-/issues/3035
|
| |\
| |
| |
| |
| |
| |
| | |
Matthiasc/for master
Closes #2319
See merge request GNOME/gtk!3140
|
| | |
| |
| |
| |
| |
| |
| |
| | |
There was an off-by-one error, making us reject sequences
of this length. But the rest of the code handles them
just fine.
Fixes: #2319
|
| | |
| |
| |
| |
| | |
This error message was misleading, as pointed out
by Ralf Jung.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Show the sequences as they are entered, using ⎄ for
the compose key, to match what IBus does nowadays.
Also handle backspace to allow corrections.
|
| | |
| |
| |
| |
| |
| | |
A bunch of keysyms for dead keys have been added since this
code was last touched. Update the check to cover the full
range from dead_grave to dead_greek.
|
| |\ \
| |/
| |
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!3139
|
| | |
| |
| |
| |
| | |
The example series only has 9 steps now. Remove remnants
of step 10.
|
| | |
| |
| |
| |
| | |
Emphasize that native dialogs aren't widgets, and are not
kept alive by GTK.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Drag fixes and cleanups
Closes #3513
See merge request GNOME/gtk!3001
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Now that we have gtk_drag_check_threshold_double(), be consistent with
other draggable widgets and make sure we don't take over a drag before a
child does.
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3513
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If multiple nested widgets have drag sources on them, both using bubble
phase, we need to reliably pick the inner one. Both of them will try to
start dragging, and we need to make sure there are no situations where the
outer widget starts drag earlier and cancels the inner one.
Currently, this can easily happen via integer rounding: start and current
coordinates passed into gtk_drag_check_threshold() are initially doubles
(other than in GtkNotebook and GtkIconView), and are casted to ints. Then
those rounded values are used to calculate deltas to compare to the drag
threshold, losing quite a lot of precision along the way, and often
resulting in the outer widget getting larger deltas.
To avoid it, just don't round it. Introduce a variant of the function that
operates on doubles: gtk_drag_check_threshold_double() and use it instead
of the original everywhere.
|
| | |
| |
| |
| | |
It was passing offsets as current oordinates.
|
