Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
*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.
|
|
|
|
Otherwise we might pick up an icon at an invalid size for a given scale.
https://bugzilla.gnome.org/show_bug.cgi?id=776896
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/53cee1de
|
|
This was missing from the last commit.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/b3b4bea5
|
|
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
|
|
This is one of the condition that needs to trigger an invalidation to
recompute layout at the correct size.
https://bugzilla.gnome.org/show_bug.cgi?id=776896
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/b257699e
|
|
So to get HiDpi support.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/31059f33
|
|
avoid deprecated:
gtk_image_menu_item_new_with_label
gtk_image_menu_item_set_image
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in caja_search_directory.c,
fixes https://github.com/mate-desktop/caja/issues/895
|
|
|
|
fallout from last commit
|
|
make it consistent with behaviour for caja-places-sidebar
|
|
|
|
This commit reverts:
https://github.com/mate-desktop/caja/commit/4c130e22b98bbc1a85747adac3b582e45d34514e
https://github.com/mate-desktop/caja/commit/ac12e6d16f4a51b3327d013781e72cfec17f3624
https://github.com/mate-desktop/caja/commit/17b3c0ca924ffcd4bd06fded98227eba626d4f0b
https://github.com/mate-desktop/caja/commit/42c8d2c3373c25d6e321be6950997c0d7ce44279
And it applies an alternative to fix the deprecated functions:
gdk_screen_get_width
gdk_screen_get_height
gdk_screen_width
gdk_screen_height
|
|
|
|
The call to gtk_render_frame() should be enough;
Now the .dnd style class setting from themes are used.
Fixes https://github.com/mate-desktop/mate-themes/issues/194
origin commit:
https://git.gnome.org/browse/nautilus/commit/?id=8d8979f
|
|
avoid deprecated:
gdk_screen_get_monitor_geometry
gdk_screen_get_monitor_at_window
|
|
|
|
When a file is a symlink to one of the XDG data dirs, we'll allow that
link to work, as they're vendor provided and not world-writeable by a
malicious entity.
This lookup is handled by the "is_system_dir" logic, to ensure that whatever
the .desktop symlink is pointing at is already implicitly whitelisted. This
allows for vendor provided "default" symlinks on within user directories,
such as installer shortcuts for LiveCDs, etc.
Signed-off-by: Ikey Doherty <[email protected]>
|
|
use max_char_width for 'Select and application to view his description'
label, as this can cause a window size jumping for this gui.
Depends on language translations.
Ie. german language was affected.
|
|
|
|
|
|
|
|
|
|
the file.
|
|
fixes https://github.com/mate-desktop/caja/issues/735
|
|
fixes https://github.com/mate-desktop/caja/issues/410
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=f1c782c13dd675bafffb2a4d85900da52be88f3f
|
|
Minimum of one column
taken from:
https://github.com/linuxmint/nemo/commit/78d4a4f
https://github.com/linuxmint/nemo/commit/21ea094
fix
|
|
fixes build warning about deprecation
ported from:
https://git.gnome.org/browse/nautilus/commit/?id=bd73a8ee91610310c3b0dfdaa69465fc48ecac8f
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=ace6d2c2170028148785f3fa87eedf883f20f1dd
GIO commit for reference:
https://git.gnome.org/browse/glib/commit/?id=510ba9b4efe1813e24c6dfa7405c3547bf9efdd7
|
|
another case of excessive gnome -> mate renaming back in 2011
|
|
it's probably some leftover from excessive gnome -> mate renaming
back in 2011. even if it ever existed, we can drop it now, like
upstream did for ~/.gnome2:
https://git.gnome.org/browse/nautilus/commit/?id=5c17044597c980bdbe77a4894d92150fbe69909c
|
|
relayouting
The GtkScrolledWindow uses the widget prefered size as a guess as to
whether scrollbars are needed or not in the automatic scrollbars case.
If we don't report anything for them we typically get it wrong and cause
two size allocate calls on the child each time, with different sizes.
This (the two sizes speicifically) will cause unnecessary relayouts of
the window.
So, we just report the current size of the layed out icons as the prefered
size. This is somewhat wrong as its depending on previous size_allocation
calls rather than the "ideal" size of the widget, but since the ideal size
is ignored anyway and just used for this it works well.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=fa6e447
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=308f4ce
|
|
|