| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
When media modules from previous versions still exist that conflict with
the now built-in modules, block loading them.
Determining the module name was done with the best way I could come up
with, because apparently g_io_module_scope_block() requires the full
library name.
|
|
|
|
| |
Instead, include them in libgtk.
|
|\
| |
| |
| |
| | |
Handle the new line height pango attribute
See merge request GNOME/gtk!3840
|
| |
| |
| |
| |
| | |
This was getting downloaded from sourceforge every
time for the docs build, and that started failing.
|
|/
|
|
|
| |
Update all the places where we switch over PangoAttributeType
to handle (and ignore, for now) the new line height attribute.
|
|\
| |
| |
| |
| | |
widget: Change callback scope
See merge request GNOME/gtk!3796
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Look who changed his mind since commit 8e2ffb3b46 :-)
The "call" scope means that the callback is only used during the
function call itself (here: gtk_widget_class_install_action()).
That's clearly wrong here, as the callback is invoked every time
the action is activated.
Arguably the "notified" scope is a better match here, where the
lack of a GDestroyNotify parameter suggests that the callback may
be used forever (which is the case here).
Related: #3498
|
|\ \
| | |
| | |
| | |
| | | |
ngl: Make current when unrealizing
See merge request GNOME/gtk!3835
|
| | |
| | |
| | |
| | |
| | | |
The profiler (at least) discards GL objects and we want to discard them
on the right context.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Cosmetics: Tweak css parser error messages
See merge request GNOME/gtk!3834
|
|/ / /
| | |
| | |
| | |
| | | |
These show up in tooltips, so they should a) be capitalized
and b) not end with a period.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gtk-demo: Spruce up the hypertext demo
See merge request GNOME/gtk!3832
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Use the newish allow-breaks pango attribute
to make the text break better.
|
|/ / /
| | |
| | |
| | | |
(cherry picked from commit 11e6ce175166364f7c807764a8de8619b65da82a)
|
| | | |
|
| | |
| | |
| | |
| | | |
(cherry picked from commit b467881274d4917fcc29ace6c699786ffa74e909)
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Revert "textview: fix yoffset position when top_margin is set"
See merge request GNOME/gtk!3828
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 908b1e5e1214afc01440bc07a8d937222f411f38.
This commit broke top-margin altogether.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
settings: Default gtk-split-cursor to FALSE
See merge request GNOME/gtk!3827
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
According to Owen, this was the intention when the setting
was added in 2001. It only took us 20 years to fix the
default value.
|
|\ \ \ \ \
| |/ / / /
| | / / /
| |/ / /
|/| | | |
text: Move setup code out of a loop
See merge request GNOME/gtk!3826
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Somebody needs to figure out why it fails in ci so
frequently.
|
| | | |
| | | |
| | | |
| | | | |
Just a cleanup, no functional change.
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Shrink shadow extents
See merge request GNOME/gtk!3825
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Long time ago, Cairo shadows in both GTK3 and 4 were drawn at a size about
twice their radius. Eventually this was fixed but the shadow extents are
still calculated for the previous size and appear unreasonably large: for
example, 141px for a 50px radius shadow. This can get very noticeable in
places such as invisible window frame which gets included into screenshots.
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3419 just divides the
radius by 2 when drawing a shadow with Cairo, do the same when calculating
extents.
See https://gitlab.gnome.org/GNOME/gtk/-/issues/3841
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
popovermenu: Cycle around focus also with (Shift+)Tab
Closes #3915
See merge request GNOME/gtk!3732
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Same thing as the previous popovermenu commit, except for the base popover
because the popovermenu needs special behaviour with e.g. sides arrow so
we need to have the "cycle around" for regular popovers here too.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently when moving the focus with (Shift+)Tab, it also traverses the window's
widgets, although it would be expected that the focus stays within the popover,
as it's (almost) like it's a separate window. This would be consistent with
the behaviour of the Up/down arrows, which do cycle around the focus once it
reaches the end.
So this commit makes the popovermenu cycle around focus in any direction, apart
from left/right because they are used to open and close submenus and it wouldn't
make sense anyway to cycle horizontally as there's usually only one widget per
line.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
treepopover: Add keynav
See merge request GNOME/gtk!3822
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Arrange for the items to be focusable, and add keyboard
activation. Still missing: cycling focus inside the
popover.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
imcontext: Treat keysyms as 32bit values
Closes #4149
See merge request GNOME/gtk!3819
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Our compose table format is still limited to 16bit
values for keysyms, but what we see in key events
can be 32bit values, and we treat them as such now.
Fixes: #4149
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove an unimplemented function
Closes #4151
See merge request GNOME/gtk!3820
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For now, these check that the surrounding handling
in GtkText and GtkTextView is sane.
Fixes: #4151
|
| | | | |
| | | | |
| | | | |
| | | | | |
This was, sadly, returning garbage.
|
| | | | |
| | | | |
| | | | |
| | | | | |
This will be used in tests.
|
|/ / / /
| | | |
| | | |
| | | | |
_gtk_entry_get_im_context does not exist.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
menusectionbox: Passthrough the focus function of custom widgets' gizmo
Closes gnome-text-editor#93
See merge request GNOME/gtk!3817
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It broke keyboard focusing any widget added through the custom widget
menu feature. So for example if you put e.g. a custom check box widget
in a menu, you won't be able to focus it.
This is because the gizmo is mostly used to custom drawing with e.g.
CSS for small visual elements like scale markers. That's probably why
gizmo's default focus overrides block the focus from going through
the children. So this commit fixes it by overriding those and passing
the focus through the children.
|
|\ \ \ \ \
| | |_|/ /
| |/| | |
| | | | |
| | | | | |
video: Use cross-fade transition to avoid resizes
See merge request GNOME/gtk!3815
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Slide animations cause changes in the size requests due to the
behavior of GtkRevealer. We can avoid those by using cross-fades, which
don't have that problem.
Besides, cross-fades look better anyway.
|
|\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
gtkgesturerotate: Fix assertion
Closes #4144
See merge request GNOME/gtk!3818
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Fixes #4144. An assertion would be printed when GtkGestureRotate was
used with a touchscreen.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
imcontext: Tweak Compose sequence preedit
Closes #10, #4127, and #4124
See merge request GNOME/gtk!3799
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove the limitation on the number of dead keys
that we match, and allow the result be be multiple
characters.
Regenerate the builtin sequences, since this changes
what dead key sequences we can reproduce algorithmically.
Update tests to match.
Fixes: #10
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make gtk_check_algorithmically take a GString
for the result. This is in preparation for allowing
multi-character results here, in the future.
Update all callers.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Treat Escape the same in hex sequences and in
Compose sequence: reset the state.
|