| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The shortcut Alt+Home should not change the items from desktop to those
in /home/<user>/
In order to fix this, the corresponding action was disabled.
https://bugzilla.gnome.org/show_bug.cgi?id=761241
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It was inverting the UI.
|
| |
|
|
|
|
| |
Forgot to add the use_underline property.
|
|
|
|
|
|
|
|
|
| |
Recently we removed gtk+ notifications from mount operations in the
gtk+ sidebar in order to move the handling of those to Nautilus.
Now that that is done, implement notifications handling for unmount
sidebar operations. The mount operations notifications are still handled
by gnome-shell, we will see if that continues making sense or not.
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit fdfcd0441f10a976cbac93e93d6ea27c9c6a42cc)
|
|
|
|
|
|
|
|
|
|
| |
We want to make them affect the action itself, but that can confuse
users that were already using them, and probably doesn't worth the
effort.
So for now make clear in the preferences window that what it affects
is showing or not the action in the menu, not the availability action
itself.
|
| |
|
|
|
|
| |
It's actually "Since...", not around.
|
|
|
|
| |
Follow what Gedit does, and use a plain "Preferences" for the tittle.
|
|
|
|
| |
It was missing.
|
|
|
|
|
|
|
|
|
|
|
| |
We want to provide priority to anything that was set on the user theme
rather than in custom Adwaita theme, in case anyone wants to override
some style.
This fixes the desktop window getting the same background as the one
defined for normal windows in the Nautilus Adwaita theme.
https://bugzilla.gnome.org/show_bug.cgi?id=761965
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With recent gtk+ changes, the notebook style and drawing was
changed somehow.
Nautilus had a white background by "luck", and the canvas view
needs to apply it's own background style in order to have a background
at all.
This commit follows what we were doing with the desktop window where we
apply a style class to have a transparent background, but in this case
a white one to fix this issue.
https://bugzilla.gnome.org/show_bug.cgi?id=761965
|
|
|
|
|
|
|
|
| |
This seems no longer necessary. It looks like it was done to avoid
flashing when redrawing, but probably this was fixed sometime in the
past, so a transparent background in a widget doesn't flash anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=761965
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=761965
|
|
|
|
|
|
|
|
|
| |
We expect any GtkWindow to actually have the window style.
So instead of changing the css node, just apply a style class.
This will be needed for upcoming patches.
https://bugzilla.gnome.org/show_bug.cgi?id=761965
|
| |
|
|
|
|
| |
(cherry picked from commit 81151d468cee60e544cba4bb32ad4b25ada68b83)
|
|
|
|
| |
(cherry picked from commit 9aa5fedb13beeb3260bfa63b4b52cc6e1d9045b2)
|
| |
|
| |
|
|
|
|
|
| |
With designers guidance, rework the preferences window to a better state.
Also, do few improvement on the way, like converting it to a GtkWindow.
|
|
|
|
| |
The label was misaligned with latest gtk+.
|
|
|
|
|
|
|
|
|
|
|
|
| |
So we can select what type of view do we want for search independently
of what we normally use.
This is needed since we default to switch to list view for search, but
we would like to allow users to select a different view. However,
instead of adding a preference in the preference dialog, we can do it
more straightforward and change the setting when we are in search.
On the way, rework all the enums and views id for a saner code...
|
|
|
|
| |
Since 3.18 is done in the menu directly.
|
|
|
|
| |
(cherry picked from commit a4638b052ccbae61016cfde7de3d8fa3c7eb5e50)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Nautilus, undoing trash operations relies on the original path of deleted
files and their deletion time. This time value is obtained after the operation
is performed, which can lead to a mismatch. This mismatch would cause deleted
files to not be restored by an undo operation, as they would not be recognised
as being the originals.
Compare the deletion time from the file in trash with the value stored in the
undo information. If the difference is less or equal than an epsilon value,
consider the files as matching.
https://bugzilla.gnome.org/show_bug.cgi?id=761819
|
|
|
|
| |
(cherry picked from commit 9efdea53e0e494d45c110321aeec56f0c6a11bfa)
|
|
|
|
| |
(cherry picked from commit 03da19aa6a8711eff3f1445fd2e29f76f026707e)
|
|
|
|
| |
(cherry picked from commit 1b619e6ac59f0c45a57cd5f1cf37728c7a5d26bb)
|
|
|
|
| |
(cherry picked from commit 9ac9d8cfc2a974632f9132c80aa69d74fc769de7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nautilus file operations are implemented as asynchronous jobs scheduled using
g_io_scheduler. Since g_io_scheduler has been deprecated, these operations
should be using the simpler GTask API. The helper functions used in the
operations have been changed in a previous patch so it is now possible to port
the jobs themselves to the new API.
The job structures are now data for tasks, which are handled by the existing
functions in separate threads. For finalizing the operations, the existing
"job_done" functions are now used as callbacks.
https://bugzilla.gnome.org/show_bug.cgi?id=761549
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nautilus file operations are implemented as asynchronous jobs scheduled using
g_io_scheduler. Since g_io_scheduler has been deprecated, these operations
should be using the simpler GTask API. In order to make this change possible, a
first step would be to replace the scheduler in the helper functions called
during the jobs.
Replace g_io_scheduler_send_to_mainloop with g_main_context_invoke in helper
functions. Since g_main_context_invoke is not blocking, add a mutex and a
condition so the current thread is blocked until the operation is completed in
the main loop.
https://bugzilla.gnome.org/show_bug.cgi?id=761549
|
|
|
|
| |
(cherry picked from commit fcd0d8b2be3d09e7e4170243951618ba1b378f28)
|
|
|
|
|
|
| |
They were missing.
https://bugzilla.gnome.org/show_bug.cgi?id=761706
|
| |
|
| |
|
|
|
|
| |
The position was set wrongly as 2 for all of them.
|
|
|
|
| |
(cherry picked from commit aa58221d98721fe92ce210bab7393843b2978f80)
|
|
|
|
| |
(cherry picked from commit 1fdd8a1399caf5f8fce4c1df3606c64f0223dfcf)
|
| |
|
| |
|