summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* media: Block loading of the old moduleswip/otte/no-media-modulesBenjamin Otte2021-08-101-2/+13
| | | | | | | | | 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.
* media: Don't build media modules as modulesBenjamin Otte2021-08-108-82/+36
| | | | Instead, include them in libgtk.
* Merge branch 'matthiasc/for-master' into 'master'Matthias Clasen2021-08-106-1/+31
|\ | | | | | | | | Handle the new line height pango attribute See merge request GNOME/gtk!3840
| * ci: Add libjpeg-turbo-devel to the Fedora imageMatthias Clasen2021-08-102-1/+3
| | | | | | | | | | This was getting downloaded from sourceforge every time for the docs build, and that started failing.
| * Handle the new line height pango attributeMatthias Clasen2021-08-104-0/+28
|/ | | | | Update all the places where we switch over PangoAttributeType to handle (and ignore, for now) the new line height attribute.
* Merge branch 'callback-annotation-again' into 'master'Matthias Clasen2021-08-101-1/+1
|\ | | | | | | | | widget: Change callback scope See merge request GNOME/gtk!3796
| * widget: Change callback scopeFlorian Müllner2021-07-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'wip/otte/for-master' into 'master'Benjamin Otte2021-08-081-1/+3
|\ \ | | | | | | | | | | | | ngl: Make current when unrealizing See merge request GNOME/gtk!3835
| * | ngl: Make current when unrealizingBenjamin Otte2021-08-081-1/+3
| | | | | | | | | | | | | | | The profiler (at least) discards GL objects and we want to discard them on the right context.
* | | Merge branch 'matthiasc/for-master' into 'master'Matthias Clasen2021-08-071-2/+2
|\ \ \ | | | | | | | | | | | | | | | | Cosmetics: Tweak css parser error messages See merge request GNOME/gtk!3834
| * | | Cosmetics: Tweak css parser error messagesMatthias Clasen2021-08-071-2/+2
|/ / / | | | | | | | | | | | | These show up in tooltips, so they should a) be capitalized and b) not end with a period.
* | | Belarusian translation: Remove broken translation stringAndre Klapper2021-08-071-1/+1
| | |
* | | Khmer translation: Strip some invisible bytes from setting translationsAndre Klapper2021-08-071-2/+2
| | |
* | | Merge branch 'matthiasc/for-master' into 'master'Matthias Clasen2021-08-071-24/+51
|\ \ \ | | | | | | | | | | | | | | | | gtk-demo: Spruce up the hypertext demo See merge request GNOME/gtk!3832
| * | | gtk-demo: Spruce up the hypertext demoMatthias Clasen2021-08-071-24/+51
| | | | | | | | | | | | | | | | | | | | Use the newish allow-breaks pango attribute to make the text break better.
* | | | Update Hebrew translationYaron Shahrabani2021-08-071-2096/+1723
|/ / / | | | | | | | | | (cherry picked from commit 11e6ce175166364f7c807764a8de8619b65da82a)
* | | Update Persian translationDanial Behzadi2021-08-071-458/+498
| | |
* | | Update Persian translationDanial Behzadi2021-08-071-995/+1032
| | | | | | | | | | | | (cherry picked from commit b467881274d4917fcc29ace6c699786ffa74e909)
* | | Merge branch 'wip/chergert/revert-top-margin' into 'master'Matthias Clasen2021-08-061-1/+1
|\ \ \ | | | | | | | | | | | | | | | | Revert "textview: fix yoffset position when top_margin is set" See merge request GNOME/gtk!3828
| * | | Revert "textview: fix yoffset position when top_margin is set"Christian Hergert2021-08-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 908b1e5e1214afc01440bc07a8d937222f411f38. This commit broke top-margin altogether.
* | | | Merge branch 'matthiasc/for-master' into 'master'Matthias Clasen2021-08-051-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | settings: Default gtk-split-cursor to FALSE See merge request GNOME/gtk!3827
| * | | | settings: Default gtk-split-cursor to FALSEMatthias Clasen2021-08-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge branch 'matthiasc/for-master' into 'master'Matthias Clasen2021-08-052-30/+34
|\ \ \ \ \ | |/ / / / | | / / / | |/ / / |/| | | text: Move setup code out of a loop See merge request GNOME/gtk!3826
| * | | ci: Disable treeview-headers-hidden reftestMatthias Clasen2021-08-051-2/+5
| | | | | | | | | | | | | | | | | | | | Somebody needs to figure out why it fails in ci so frequently.
| * | | text: Move setup code out of a loopMatthias Clasen2021-08-051-28/+29
| | | | | | | | | | | | | | | | Just a cleanup, no functional change.
* | | | Merge branch 'wip/exalm/shadow-extents' into 'master'Matthias Clasen2021-08-052-7/+7
|\ \ \ \ | |/ / / |/| | | | | | | | | | | Shrink shadow extents See merge request GNOME/gtk!3825
| * | | Shrink shadow extentsAlexander Mikhaylenko2021-08-042-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge branch 'fix-tab-not-captured-in-popover' into 'master'Matthias Clasen2021-08-052-6/+69
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | popovermenu: Cycle around focus also with (Shift+)Tab Closes #3915 See merge request GNOME/gtk!3732
| * | | | popover: Cycle around focus with (Shift+)Tabvanadiae2021-08-041-2/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | popovermenu: Cycle around focus also with (Shift+)Tabvanadiae2021-08-041-4/+13
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | Merge branch 'combobox-keynav' into 'master'Matthias Clasen2021-08-031-8/+57
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | treepopover: Add keynav See merge request GNOME/gtk!3822
| * | | | treepopover: Start adding keynavMatthias Clasen2021-08-021-8/+57
|/ / / / | | | | | | | | | | | | | | | | | | | | Arrange for the items to be focusable, and add keyboard activation. Still missing: cycling focus inside the popover.
* | | | Merge branch 'big-keysyms' into 'master'Matthias Clasen2021-08-034-24/+24
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | imcontext: Treat keysyms as 32bit values Closes #4149 See merge request GNOME/gtk!3819
| * | | | imcontext: Treat keysyms as 32bit valuesMatthias Clasen2021-08-024-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | Merge branch 'surround-test' into 'master'Matthias Clasen2021-08-035-2/+164
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | Remove an unimplemented function Closes #4151 See merge request GNOME/gtk!3820
| * | | | Add some GtkIMContext testsMatthias Clasen2021-08-022-0/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For now, these check that the surrounding handling in GtkText and GtkTextView is sane. Fixes: #4151
| * | | | textview: Fix the get_surrounding implementationMatthias Clasen2021-08-021-1/+1
| | | | | | | | | | | | | | | | | | | | This was, sadly, returning garbage.
| * | | | Add a private getter for the textview key controllerMatthias Clasen2021-08-022-0/+8
| | | | | | | | | | | | | | | | | | | | This will be used in tests.
| * | | | Remove an unimplemented functionMatthias Clasen2021-08-021-1/+0
|/ / / / | | | | | | | | | | | | _gtk_entry_get_im_context does not exist.
* | | | Merge branch 'fix-custom-widget-menu-focus' into 'master'Matthias Clasen2021-08-021-1/+20
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | menusectionbox: Passthrough the focus function of custom widgets' gizmo Closes gnome-text-editor#93 See merge request GNOME/gtk!3817
| * | | | menusectionbox: Passthrough the focus function of custom widgets' gizmovanadiae2021-08-021-1/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge branch 'wip/otte/for-master' into 'master'Matthias Clasen2021-08-021-1/+1
|\ \ \ \ \ | | |_|/ / | |/| | | | | | | | | | | | | video: Use cross-fade transition to avoid resizes See merge request GNOME/gtk!3815
| * | | | video: Use cross-fade transition to avoid resizesBenjamin Otte2021-08-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge branch 'fix-4144' into 'master'Matthias Clasen2021-08-021-5/+5
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | gtkgesturerotate: Fix assertion Closes #4144 See merge request GNOME/gtk!3818
| * | | | gtkgesturerotate: Fix assertionJames Westman2021-08-021-5/+5
|/ / / / | | | | | | | | | | | | | | | | Fixes #4144. An assertion would be printed when GtkGestureRotate was used with a touchscreen.
* | | | Merge branch 'input-tweaks' into 'master'4149-imcontext-handle-16bit-keysymsMatthias Clasen2021-08-028-306/+272
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | imcontext: Tweak Compose sequence preedit Closes #10, #4127, and #4124 See merge request GNOME/gtk!3799
| * | | | imcontext: Code cleanupMatthias Clasen2021-07-291-35/+15
| | | | |
| * | | | composetable: Allow multiple dead keysMatthias Clasen2021-07-296-212/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | | composetable: Change an APIMatthias Clasen2021-07-294-39/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | imcontext: Handle Escape in Compose sequenceMatthias Clasen2021-07-291-6/+12
| | | | | | | | | | | | | | | | | | | | | | | | | Treat Escape the same in hex sequences and in Compose sequence: reset the state.