- 25 Jul, 2022 1 commit
-
-
- 06 Apr, 2022 1 commit
-
-
- 03 Feb, 2022 1 commit
-
-
- 17 Jan, 2022 1 commit
-
-
- 08 Jan, 2022 1 commit
-
-
The desktop icons extension can get into a state where the desktop no longer takes mouse input. This happens if a user starts a rubber banding operation and then drags the mouse to somewhere on screen that has a pop up menu, and then pops the menu up. This commit addresses the bug by limiting the grab actor to the backgrounds, and by explicitly ending the rubber banding operation when one of the icons own menus is shown. One side effect of limiting the grab actor to the backgrounds, is the rubber banding code never gets to see motion outside of the backgrounds anymore. In order to keep drag operations feeling fluid when the user moves toward the edge of the screen, this commit also overrides the grab helpers captured-event handler so those motion events keep coming. We also start to end the rubber band if for any reason the grab it had was released.
-
- 07 Jan, 2022 1 commit
-
-
- 09 Dec, 2021 1 commit
-
-
- 17 Nov, 2021 1 commit
-
- 08 Sep, 2021 1 commit
-
-
- 04 Sep, 2021 1 commit
-
-
- 03 Jun, 2021 1 commit
-
-
When the icon can't be found, the icon is empty on desktop.
-
- 09 May, 2021 1 commit
-
-
- 03 Apr, 2021 3 commits
-
-
- 28 Mar, 2021 1 commit
-
-
Kuroe-Hanako authored
-
- 24 Feb, 2021 1 commit
-
-
- 03 Feb, 2021 1 commit
-
-
- 27 Jan, 2021 1 commit
-
-
Carlos Garnacho authored
Imitate the behavior of Nautilus canvas WRT double clicks being handled on all of the icon(s) without accounting for the double click distance. As the extension does already lean on Nautilus look & feel, it seems to make sense doing this. This is not as crucial for mice as it is for touchscreens, where the default 5px limit may be a bit on the short side depending on device sensitivity.
-
- 09 Jan, 2021 1 commit
-
-
Sergio Costas authored
-
- 06 Dec, 2020 1 commit
-
-
When several files are selected and the user tries to drag them, only one is dragged. This patch fixes it. Fix #211
-
- 04 Dec, 2020 1 commit
-
-
Daniel van Vugt authored
Since around about mutter 3.37, `clutter_actor_get_transformed_position` no longer forces/guarantees allocation has actually happened, and if not will just return NaN values. Those NaNs propagated into the gnome-shell drag-and-drop functions which can't handle them and so dragging would fail, or worse, never complete and lock the user out of interacting with the desktop. Now we force allocation of the actor being dragged before requesting the drag begins and the gnome-shell drag-and-drop functions work properly. You still can't drag and drop into Nautilus windows but at least the icons now animate, snap back, and don't lock the mouse. We have to predicate this fix on `get_fixed_position` existing as a way of testing the newer allocation API (and the bug itself) exists. Just like we did in 72b20c9c. Fixes: #224 https://bugs.launchpad.net/bugs/1898462
-
- 29 Nov, 2020 2 commits
-
-
Since the environment for use an external GPU is set only for .desktop files, this patch ensures that it is shown only for those files.
-
marsch84 authored
It is not possible to start applications with the dedicated graphics card after the change to the native switcheroo controller. It looks like the unpack function of the GLib Variant does not fully process the "GPUs" data structure. Added code to look up the atributes where needed.
-
- 28 Nov, 2020 7 commits
-
-
If an existing one hadn't run yet then we could end up with two or more idlers scheduled to call `this._layoutChildren()`. And both would appear to succeed, except that the second and subsequent ones would silently fail `clutter_actor_add_child` in `st_bin_set_child`, called from: ``` _addFileItemTo(fileItem, column, row, coordinatesAction) { let placeholder = this.layout.get_child_at(column, row); placeholder.child = fileItem; ``` But `StBin` doesn't check for such failure and keeps a copy of its own `priv->child` even for those actors that it failed to parent. So for those, `st_bin_remove` would never be called and some time later this assertion will fail: ``` st_bin_destroy (ClutterActor *actor) { StBinPrivate *priv = st_bin_get_instance_private (ST_BIN (actor)); if (priv->child) clutter_actor_destroy (priv->child); g_assert (priv->child == NULL); ``` Arguably `st_bin_set_child` should have detected the failure of `clutter_actor_add_child` in the first place and so not kept a copy of `priv->child`. But regardless, calling `_layoutChildren()` too many times is the root cause. So don't do that. Fixes: https://bugs.launchpad.net/bugs/1898005 but may also fix some leaks.
-
Sergio Costas authored
-
Marco Trevisan authored
While the desktop will work even in previous versions, some features would just be broken, so it's time to bump again the dependency
-
Marco Trevisan authored
Old classes are gone, we need to follow this new pattern now
-
Marco Trevisan authored
We don't have to manage this via dbus anymore as the shell exposes these properties now. While it has not anymore the switcheroo xml interface exported, so the extension should ship it instead.
-
Marco Trevisan authored
Otherwise new shell will complain about the multiple arguments
-
-
- 21 Nov, 2020 1 commit
-
-
- 01 Nov, 2020 1 commit
-
-
- 23 Sep, 2020 1 commit
-
-
- 20 Sep, 2020 1 commit
-
-
- 12 Sep, 2020 1 commit
-
-
- 10 Sep, 2020 1 commit
-
-
- 08 Sep, 2020 1 commit
-
-
- 06 Sep, 2020 1 commit
-
-
- 05 Sep, 2020 1 commit
-
-