- 23 Jan, 2021 1 commit
-
- 22 Jan, 2021 1 commit
-
-
Danial Behzadi authored
-
- 21 Jan, 2021 3 commits
-
-
Sebastian Keller authored
The code previously was using CSS to define row/column spacing and padding which was combined with a subicon size computed in code relative to the requested icon size. In smaller icon sizes it was possible for the CSS spacing+padding + the size of the two subicons to exceed the requested icon size. This then would lead to the label being pushed down for app folders compared to other icons. Another more severe issue caused by this would happen if the first item in an icon grid was an app folder. Then the calculation for the maximum allowed icon size could be off, leading to all icons in the grid becoming smaller than actually necessary. This commit changes this to use homogeneous row and column layouts to evenly distribute the remaining spacing instead of using a fixed CSS value. Fixes #3069 Part-of: <!1581>
-
Florian Müllner authored
With the new position, the dash is now stronger connected to the app grid than it used to; reflect that by showing apps either in the grid or the dash, not both (except for non-favorite running apps). Teams/Design/os-mockups#88 Part-of: <!1580>
-
Sebastian Keller authored
It was possible to switch workspaces by quickly dragging the workspace immediately after clicking on a window during the transition from the overview. This is unlikely something that is intentionally used but can be confusing and look bad when triggered accidentally. Fixes #2993 Part-of: <!1578>
-
- 20 Jan, 2021 1 commit
-
-
Florian Müllner authored
We don't want the dash to expand, but if it's given more space than requested, we want it to be positioned at the bottom. Part-of: <!1577>
-
- 19 Jan, 2021 9 commits
-
-
Sebastian Keller authored
This is some leftover from code that was used to keep track of volumes added/removed while the screen was locked before the move to a components system in 2a800e4c. All that the remaining code does is filter devices from an empty list. Part-of: <!1579>
-
Balázs Úr authored
-
Florian Müllner authored
Now that the dash is always visible, it doesn't make sense to keep it in a separate layer from the main overview group and use a separate spacer actor as a placeholder. Part-of: <!1575>
-
Jakub Steiner authored
- use a light, nostroke dash - boost border radius globally Part-of: <!1559>
-
Georges Basile Stavracas Neto authored
Now that the Dash is horizontal, the popup menu of the Dash icons must show up, instead of left/right. Make AppIcon.popupMenu() receive an optional parameter with the side to show the menu, using St.Side.LEFT as default. Override this method in DashIcon to always pass St.Side.TOP. Part-of: <!1559>
-
Abderrahim Kitouni authored
Part-of: <!1559>
-
Georges Basile Stavracas Neto authored
And move it to the bottom of the overview. Change the height-based calculation of the icon sizes to be width-based. Put the DashFader in a vertical box, and make all corners of the Dash equally rounded. Part-of: <!1559>
-
Georges Basile Stavracas Neto authored
The Dash will need only the fading aspect of SlidingControl in the next commit. Part-of: <!1559>
-
Georges Basile Stavracas Neto authored
Part-of: <!1559>
-
- 18 Jan, 2021 3 commits
-
-
Florian Müllner authored
-
Florian Müllner authored
Like the mutter 40.alpha.1.1 release, we missed adjusting to a GSettings schema move from g-s-d to gsettings-desktop-schemas, resulting in an abort on startup with the latest released gnome-settings-daemon.
-
Florian Müllner authored
Between the GTK4 port and the latest GTK4 version, calling realize() on a newly created window to force its surface to be created stopped working. So instead, wait for the window to get realized regularly to set its parent. Part-of: <!1574>
-
- 17 Jan, 2021 1 commit
-
-
Fabio Tomat authored
-
- 16 Jan, 2021 1 commit
-
-
Marek Černocký authored
-
- 15 Jan, 2021 3 commits
-
-
Florian Müllner authored
Mouse settings moved from gnome-settings-daemon to gsettings-desktop-schemas, and we missed adjusting the shell side. Part-of: <!1573>
-
Marek Černocký authored
-
Марко М. Костић (Marko M. Kostić) authored
-
- 14 Jan, 2021 17 commits
-
-
Georges Basile Stavracas Neto authored
It now requires both application-id and contact-info to properly set the enabled providers. Part-of: <!1571>
-
Florian Müllner authored
-
Florian Müllner authored
Update NEWS.
-
Florian Müllner authored
The shader code currently only accounts for padding for the bottom and right fades, but not for top and left. As a result, we only fade the right edge when swiping through app picker pages, whoops. Part-of: <!1569>
-
Florian Müllner authored
Part-of: <!1570>
-
Florian Müllner authored
With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <!1495>
-
Florian Müllner authored
In GTK4, all widgets are reactive, and therefore GtkEventBox has been removed. In order to make the upcoming GTK4 port a bit cleaner, remove the expander's event box now. Part-of: <!1495>
-
Florian Müllner authored
We currently use separate frames for the details expander and the expanded details. That layout works as long as frames are boxy (as in the default GTK3 style), but breaks down with rounded corners (as in the default GTK4 style). In order to work with either style, adapt the layout to use a single surrounding frame and appropriate borders as separator. Part-of: <!1495>
-
Florian Müllner authored
Toolbars have been removed from GTK4, so just use a regular GtkBox for the error details bottom bar. Part-of: <!1495>
-
Florian Müllner authored
The interface has been removed in GTK4, so use widget-specific API for adding children where possible. Part-of: <!1495>
-
Florian Müllner authored
The property has been removed in GTK4, so prepare for a port by setting the four individual margin properties instead. Part-of: <!1495>
-
Florian Müllner authored
GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <!1495>
-
Florian Müllner authored
GTK4 will remove the GtkHeaderBar:title property, so stop using it and set the window's title property instead, as that's what headbars use in both GTK3 and GTK4 unless explicitly overridden. Part-of: <!1495>
-
Florian Müllner authored
There's little point in setting properties to their default value, so stop doing that. (GtkFrame:shadow-type actually defaults to "edged-in" rather than "in", but all types other than "none" are treated the same nowadays) Part-of: <!1495>
-
Florian Müllner authored
Unlike in previous GTK version (or Clutter), destroy() no longer breaks reference cycles but just releases the reference held by GTK itself. So any reference we hold - either the explicit property or any signal handlers that bind the window as `this` - prevents the window from being disposed when closed, and the application won't quit. Work around this by explicitly running dispose() on the window when it is removed from the application. Part-of: <!1495>
-
Florian Müllner authored
The property has been removed in GTK4, so prepare for a port by setting the four individual margin properties instead. Part-of: <!1495>
-
Florian Müllner authored
Use the text-direction-aware start/end variants instead. Part-of: <!1495>
-