Age | Commit message (Collapse) | Author | Files | Lines |
|
With a lower starting interval, the UI responds more quickly, and
loading tends to complete faster.
Ported from
github.com/linuxmint/nemo/commit/61368e3fc33c0d662f45731d6bbb2a28fc5023ca
Where these benchmarks resulted for Nemo:
NEMO_BENCHMARK_LOADING=1 nemo /usr/bin
with:
Nemo startup time: 1.797009 seconds
Folder load time: 0.937992 seconds
Idle...Folder load time: 0.973764 seconds
without:
Nemo startup time: 2.054006 seconds
Folder load time: 1.187159 seconds
Idle...Folder load time: 1.219712 seconds
Speedup on opening a Caja folder with many files was immediate and obvious
|
|
|
|
|
|
This reverts commit fd1f45f308e418d1c1b44b968ce83f77e4f8a689.
|
|
This reverts commit 04f7e80725c61ab511e2a4ead45eb31acc026e1a.
|
|
This reverts commit 424cf4485515a51074c0811880560de360dad784.
|
|
|
|
|
|
|
|
|
|
If true the gsettings key "ctrl-tab-switch-tabs" into "org.mate.caja.preferences"
Closes https://github.com/mate-desktop/caja/issues/768
|
|
Fixes https://github.com/mate-desktop/caja/issues/1024
|
|
Stop crash and g_object_ref: assertion 'G_IS_OBJECT (object)' failed warnings on toggling desktop_is_home_dir and on some window opening events
|
|
Apply one part of https://github.com/GNOME/nautilus/commit/c039b03590c86f5142c78d616700ef7af7c8a5a8#diff-f896071d07d34e87af94a18de95e4ea2
|
|
Apply github.com/GNOME/nautilus/commit/e759e82386f80fb214a420b789b07a194480462c
pathbar: Fix crash when accessing drive root
The path bar button data is not properly set up when type button type is
“root”.
|
|
and avoid deprecated 'gtk_widget_override_background_color'
|
|
Fixes https://github.com/mate-desktop/caja/pull/1004#issuecomment-398140812
|
|
|
|
Screen readers need to distinguish between the desktop window and normal
windows, to be able to provide nicer speech synthesis.
This can be done by simply adding an "is-desktop" attribute to the
underlying AtkObject.
This is here done by introducing a thin caja_desktop_window_accessible_class
class which is based on GtkWindowAccessible and just appends the
attribute.
Closes: #999
|
|
Fixes https://github.com/mate-desktop/caja/pull/1005#issuecomment-394805519
|
|
|
|
|
|
|
|
|
|
not needed after ddf6f38db4e842abecd4f2ee77012050822b3775
|
|
|
|
in favor of constant using of gtk_menu_popup_at_widget
for mouse and keyboard events.
|
|
Replace deprecated gtk_menu_popup in eel-editable-label,caja-dnd, emblem-sidebar,caja-side-pane, fm-tree-view, caja-navigation-window-pane, and caja-zoom-control
|
|
|
|
|
|
|
|
|
|
|
|
Adapt and apply these four relevent Nautilus commits, which remove the code responsible for the segfaults:
*https://github.com/GNOME/nautilus/commit/e1ad3c05a6cd08c8cbf18ae53701dd742249d5fd#diff-f896071d07d34e87af94a18de95e4ea2
"pathbar: add a path-event signal"
*https://github.com/GNOME/nautilus/commit/875efc324f8e91f2d157c7532fe5570c1de421c7#diff-f896071d07d34e87af94a18de95e4ea2
"pathbar: remove unused code"
*https://github.com/GNOME/nautilus/commit/cfa51e6702ade6a8ca9045791773e6e10560262f
"window-pane: use the path-event signal from NautilusPathBar" (now CajaPathBar)
*https://github.com/GNOME/nautilus/commit/2759def4968f89c1a2370ca5b2b91af84dc4afd3
"pathbar: add a return value from path-event signal"
|
|
This was introduced in commit b28445b3d2c42a7d2dbac97983d007e4ab58684d
but has never been added to some parts of the UI.
|
|
|
|
The basenames of files are split by dots and then starting from the end
each segment is compared to find a sort order. Example:
bar.tar.bz2
foo.tar.bz2
a.bar.gz
x.tar.gz
z.tar.gz
test.tex
A heuristic determines what extension segments are part of the
extension. There is probably no perfect solution but there are much
less false positives. As a result the sorting is more intuitive and the
displayed column in the list view is better readable and displays
extensions more accurately.
In addition a bug related to the default sort criteria in the
preferences has been fixed.
|
|
|
|
avoid deprecated:
gtk_image_menu_item_set_always_show_image
gtk_image_menu_item_new_with_label
gtk_image_menu_item_set_image
|
|
*caja-pathbar: fix warning,and in the process maybe fix occasional segfaults on opening mounted volumes from the desktop
*caja-icon-info: Stop gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF (pixbuf)' failed warning by handling NULL return from function finding the pixbuf
caja-icon-canvas-item-c: do not use g_object_unref where it does not work Stop the g_object_unref: assertion 'G_IS_OBJECT (object)' failed warnings on closing icon views
|
|
|
|
This allows icons in most places to scale up properly for HiDPI
displays.
|
|
As it is deprecated, instead of using gdk_screen_get_monitor_scale_factor
use gdk_monitor_get_scale_factor().
https://bugzilla.gnome.org/show_bug.cgi?id=779774
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/273e6efc
|
|
As we now store surfaces in the GtkListStore, we have to change the
drag method to use it instead of a pixbuf.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/18a380af
|
|
|
|
This was missing from the last commit.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/3a6053f1
|
|
Port the rendering of icons to cairo surfaces, so that we can apply the
GDK scale factor when rendering icons.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/0d4555d7
|
|
The problem is that in the function canvas_container_set_workarea the screen width
and height are in "application pixels" while the workarea ones are in "device
pixels" so when the scaling is > 1, the margins are not properly setted.
We need to scale-down the workarea geometries to "application pixels".
https://bugzilla.gnome.org/show_bug.cgi?id=769302
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/315a55df
|
|
avoid deprecated:
gtk_image_menu_item_new_with_label
gtk_image_menu_item_set_image
|
|
avoid deprecated:
gtk_image_menu_item_new_with_mnemonic
gtk_image_menu_item_set_image
|