summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 3.22.243.22.24Matthias Clasen2017-10-042-2/+10
|
* Fix several issues with resizingMatthias Clasen2017-10-041-14/+7
| | | | | | Some of the border windows were not placed correctly. Patch by Jan Steffens.
* wayland: Fix a typoMatthias Clasen2017-10-041-1/+1
| | | | | | We were not setting the right tiling hint in some cases. Patch by Jan Steffens.
* ComboBox: Don’t try to remove grab on NULL deviceDaniel Boles2017-10-041-2/+4
| | | | | gtk_device_grab_remove() quite rightly expects a non-NULL GdkDevice, and we already have a branch ensuring that, into which we can move this call
* TreeMenu: Remove accidentally duplicated doc linesDaniel Boles2017-10-042-4/+1
| | | | | Not that it actually matters, as this is not public anymore, but this was done accidentally. Also, sync a property description to ComboBox.
* testcombo: Test grid :row- and :column-span-columnDaniel Boles2017-10-041-23/+27
| | | | | | | | | | | | | | Ditch two items that were white and so weren’t visible on our standard theme anyway, and use the new space to test extra grid-mode properties. Note that if we do this then, as before, we set the ListStore on the ComboBox before appending to it, that produced runtime warnings like: Gtk-CRITICAL **: gtk_menu_attach: assertion 'left_attach < right_attach' failed I didn’t look into that yet, but it may indicate that attaching items vs. recognising their spans don’t occur in the correct order. For the purposes of testing this, I just create the CB after filling its model.
* ComboBox|TreeMenu: Slightly clarify wrap-width docDaniel Boles2017-10-042-6/+4
|
* ComboBox|TreeMenu: Clarify :row|column-span-columnDaniel Boles2017-10-042-16/+15
| | | | | | | | | | | | ComboBox and TreeMenu warned in the doc for :row-span-column that the value must not exceed :wrap-width, but :wrap-width does not interact with the number of rows; it’s the :column-span-column that’s relevant. Also: Warn that spans must be > 0 for rows too, and that column spans <= :wrap-width are also not useful for items at menu column positions > 0. Finally, refer to items having spans, not values, as we were already talking about values in the model (and rows in the menu).
* 3.22.233.22.23Matthias Clasen2017-10-032-2/+9
|
* HighContrast: set min-height for headerbarsMarco Trevisan (Treviño)2017-10-033-2/+23
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=784562
* HighContrast: don't select .titlebar when is an headerbarMarco Trevisan (Treviño)2017-10-033-39/+39
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=784562
* window: Add individual CSS classes based on edge constraintsGeorges Basile Stavracas Neto2017-10-034-22/+101
| | | | | | | | | | | | The last touch on this patch series is making GtkWindow able to selectively adjust various UI details based on the different tiled edges. The main driver here is that we don't want to show shadows on edges that are constrained. This patch adds the necessary code to do that, while still maintaining compatibility with the old ways. https://bugzilla.gnome.org/show_bug.cgi?id=783669
* x11: Add support for _GTK_EDGE_CONSTRAINTS atomGeorges Basile Stavracas Neto2017-10-032-15/+193
| | | | | | | | | Following the previous patch, where edge constraints support was added to the Wayland backend, this patch introduces the necessary code to handle the _GTK_EDGE_CONSTRAINTS atom from X11 backend. https://bugzilla.gnome.org/show_bug.cgi?id=783669
* wayland: consider edge constraints in surface configurationGeorges Basile Stavracas Neto2017-10-033-4/+74
| | | | | | | | | | | | Now that GTK windows have the ability to properly handle per-edge tiling constraints, this patch extends GTK's internal Wayland protocol to have a proper enum with the relevant edge data. Once this approach is validated, we can think of upstreaming this work as an official Wayland protocol extension. https://bugzilla.gnome.org/show_bug.cgi?id=783669
* window: handle tiled edges separatelyGeorges Basile Stavracas Neto2017-10-031-124/+257
| | | | | | | | | | | | | | | | | | GTK windows don't have their tiling states really hooked into the client-side decoration code, and the only effect it has is disabling the resizing edges. With the introduction of per-edge tiling information, we are backed by much more precise data on how the window manager wants the app to behave. This patch, then, fixes GtkWindow to take into account per-edge tiling information. For compatibility purposes, the previous tiled field was kept, and thing will just continue working if no edge information is supplied. https://bugzilla.gnome.org/show_bug.cgi?id=783669
* gdk: introduce edge constraint statesGeorges Basile Stavracas Neto2017-10-031-10/+27
| | | | | | | | | These states will be consumed by GtkWindow in order to have better edge management on tiling situations. Their values are supplied by the compositor, and will be send through and X11 Atom or a Wayland protocol extension. https://bugzilla.gnome.org/show_bug.cgi?id=783669
* widget-factory: Demo different Frame border-stylesDaniel Boles2017-10-022-7/+38
| | | | | This shows not all, but the interesting/less predictable styles, and the ones that correspond to the :shadow-types that were here before.
* Revert "widget-factory: Usefully demo Frame shadow types"Daniel Boles2017-10-021-3/+36
| | | | | | | This reverts commit 15a3747406b7762518a5e573099786befb7b599d. There is a way to get different kinds of borders: it's CSS. It's better to keep the 4 Frames and demo the different styles we can do using CSS.
* Frame: Enhance CSS docsDaniel Boles2017-10-021-5/+6
| | | | | Note optional .flat class and that the old shadow types are replaced by CSS border-style et al.; quote names of nodes & classes for readability.
* 3.22.223.22.22Matthias Clasen2017-10-022-2/+29
|
* Widget: Fix obvious copypasto in set_mapped() docDaniel Boles2017-10-011-1/+1
|
* docs: css-properties: Fix wrongly repeated colourDaniel Boles2017-09-291-1/+1
|
* flowbox: Fix annotation for GListModel binding callbackSam Thursfield2017-09-271-2/+2
| | | | | | | | | | | | The GtkFlowBoxCreateWidgetFunc type lacked GObject Introspection annotations for its arguments. This made gtk_flow_box_bind_model() unusable from Python as the callback function would be passed useless values. The annotations that I've added match those of the similar callback type GtkListBoxCreateWidgetFunc. https://bugzilla.gnome.org/show_bug.cgi?id=780758
* gdk-wayland: Do not leak dummy 1x1 surface on every drawDaniel Elstner2017-09-261-6/+9
| | | | | | | | When using EGL, neither leak nor re-create the dummy 1x1 Cairo surface every time gdk_wayland_window_ensure_cairo_surface() is called. https://bugzilla.gnome.org/show_bug.cgi?id=775126
* Button: Annotate set_image() argument as nullableDaniel Boles2017-09-241-1/+1
| | | | Passing NULL is valid and results in the image child being unset/removed
* Label: Replace allow-none with nullable/optionalDaniel Boles2017-09-241-6/+6
|
* emojichooser: Plug a memory leakTimm Bäder2017-09-241-1/+2
|
* Fix broken translations of 'calendar:' settings (ignored translator comments)Andre Klapper2017-09-2410-18/+18
|
* Update Persian translationsArash Mousavi2017-09-221-395/+466
|
* ToolItem: Fix nullable annotation put on wrong argDaniel Boles2017-09-201-2/+2
| | | | D’oh
* gdkseatdefault: Grab touch events where applicableDaniel Boles2017-09-201-1/+14
| | | | | | | | | | | | | | | | | | gdk_seat_default_grab() grabs POINTER_EVENTS if the capability is GDK_SEAT_CAPABILITY_ALL_POINTING. But that enumerator is a union that includes GDK_SEAT_CAPABILITY_TOUCH, but we never grabbed TOUCH_EVENTS, an unused macro that was presumably created with this purpose in mind. So, check which of the ALL_POINTING capabilities we have, and set the right mask of POINTER_EVENTS and/or TOUCH_EVENTS as required. As part of this, explicitly let TABLET_STYLUS take over pointer events, as this is the intended behaviour and was the effective result before. This should fix touch events being lost in migrating from Device.grab() to Seat.grab(GDK_SEAT_CAPABILITY_ALL_POINTING), as found by Inkscape. https://bugzilla.gnome.org/show_bug.cgi?id=781757
* Overlay: Document style classes added per positionDaniel Boles2017-09-201-0/+6
|
* Update Polish translationPiotr Drąg2017-09-191-86/+86
|
* Window: Clarify documentation of set_application()Daniel Boles2017-09-191-3/+11
| | | | | | | | | | | | | Clarify that ::destroy, not ::hide*, removes a window from its app, by replacing the mention of open windows with the blurb on destruction from :application, completing commit 7db4bee4b62bc9b6f20ba4e599e8d030314984fd Also link to the equivalent gtk_application_(add|remove)_window() calls, since Application.add_window() already links back to Window:application. * unless you use gtkmm… https://bugzilla.gnome.org/show_bug.cgi?id=639931
* PlacesSidebar: Avoid unused mem if !CLOUDPROVIDERSDaniel Boles2017-09-191-2/+3
| | | | | The member GList *cloud_rows is only ever used if HAVE_CLOUDPROVIDERS is defined, so don’t declare it if not.
* PlacesSidebar: Unref cloud_manager in dispose()Daniel Boles2017-09-181-0/+4
| | | | | | | We ref the CloudProviders singleton in init() but did not unref it in dispose(). Do so, using g_clear_object(). https://bugzilla.gnome.org/show_bug.cgi?id=787600
* SidebarRow: Unref CloudProvider on change/finalizeDaniel Boles2017-09-181-7/+4
| | | | | | | | | | | | | It was never unref()d, either when replacing the existing GObject in set_property(), cleaning up in finalize(), or becoming a placeholder. Fix by using g_set_object() and g_clear_object() to unref as needed. This also drops the check that the newly set object is a valid cloud provider account, as we don’t do the equivalent for any of the other object-typed properties, and Carlos didn’t think this was important. https://bugzilla.gnome.org/show_bug.cgi?id=787600
* Update Swedish translationAnders Jonsson2017-09-181-135/+135
|
* Adwaita: Fix color of focus outline on colorswatchDaniel Boles2017-09-163-8/+24
| | | | | | | | | | | | | | | The focus outline disappeared as the colour of the swatch got close to the normal focus outline colour, which is alpha(currentColor, 0.3). Fix by making the outline an alpha’d version of the tick colour, but more opaque than normal outlines. 0.6 seems good enough; feel free to improve it, but at least this ensures the outline can’t vanish anymore. HighContrast achieves this already because it applies the color property to the main node, not the overlay. Doing that means the outline is fully opaque, which is fine for HC obviously but was excessive for Adwaita. https://bugzilla.gnome.org/show_bug.cgi?id=787757
* Adwaita: dark: Make colorswatch.light tick visibleDaniel Boles2017-09-163-11/+11
| | | | | | | | | | | | | | | It used $text_color unconditionally, but in :dark, text is white, so we overlaid a white tick on any light colours, all the way to white itself. Using these named colours doesn’t make practical or semantic sense. Instead, use white/black over dark/light swatches, as in HC, so all variant–swatch combos work. Light looks the same, & :dark works now. For backdrop, use alpha 0.5, unlike 0.7 in HC, as that seemed excessive & different from the current effect. 0.5 is almost identical to how $backdrop_fg_colour is a 50% mix of $fg_color, & matches backdrop text. https://bugzilla.gnome.org/show_bug.cgi?id=787531
* Expander: get_label() return is nullableDaniel Boles2017-09-151-2/+2
| | | | Also, use gchar to match the header.
* Expander: Annotate new()’s label arg as nullableDaniel Boles2017-09-141-1/+1
| | | | to match new_with_mnemonic()
* Expander: Replace (allow-none) with (nullable)Daniel Boles2017-09-141-3/+3
| | | | The former is deprecated in favour of the latter.
* Expander: Explain how to conditionally style arrowDaniel Boles2017-09-141-2/+2
|
* Spinner: Document how to select on animated in CSSDaniel Boles2017-09-141-1/+2
| | | | This is not particularly obvious, so it seems worth including.
* gtk-demo/theming: Don’t mislead about raised classDaniel Boles2017-09-141-2/+2
| | | | | | | | | | | | | | This class is not added by any widgets nor themed by Adwaita/HC. However, it is presented here as if it does something. It doesn’t. But we changed the 2 buttons with the .raised class to use symbolic icons, unlike their ‘unraised’ counterparts, which is unnecessarily confusing and might make people think .raised affects icons somehow. So, make them use the same icons in all cases; that way, if .raised is ever made to do anything, 6 years later, what it does will be clear. https://bugzilla.gnome.org/show_bug.cgi?id=644248
* gtk-demo/Makefile: Really get deps of C GResourceDaniel Boles2017-09-141-1/+1
| | | | | The XML resides in $(srcdir), not $(builddir); it is not a built source. Using the latter, changes to the referenced files did not cause rebuild.
* widget-factory: Usefully demo Frame shadow typesDaniel Boles2017-09-141-36/+3
| | | | | | Instead of showing the 4 types except for GTK_SHADOW_NONE, which are all treated identically and provide no way for themes to differentiate, just keep 2 Frames, and make one of them GTK_SHADOW_NONE to demo a flat Frame
* Frame: Add missing fixed-width format to enumsDaniel Boles2017-09-131-3/+3
|
* FlowBox: Explain how to avoid inflated min sizeDaniel Boles2017-09-121-0/+4
| | | | | | | | | | | | along the orthogonal orientation. It seems a FlowBox on its own can only handle being shrunk along its main orientation. The orthogonal requests a huge min size – reserving what it would need if the main orientation got its min size, which would flow all children in 1 line orthogonally. Adding it to a ScrolledWindow (any policy) enables free shrinking, so size_allocate() can reflow how users in this situation probably expect. https://bugzilla.gnome.org/show_bug.cgi?id=787021
View Lorry Controller Status