Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Fixes Clang static analyzer warnings:
fm-desktop-icon-view.c:331:33: warning: 1st function call argument is an uninitialized value
if (pointer == NULL && (gdk_device_get_source (cur) == GDK_SOURCE_MOUSE)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~
fm-desktop-icon-view.c:335:34: warning: 1st function call argument is an uninitialized value
if (keyboard == NULL && (gdk_device_get_source (cur) == GDK_SOURCE_KEYBOARD)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
taken from:
https://github.com/linuxmint/nemo/commit/89090ac192638d75359876d917b6d3ce106196af
|
|
Fix #1198 "Context menu with menu key broken"
Pass "NULL" for event which is passed ultimately to gtk_menu_popup_at_pointer as an invalid event was being passed when the menu key was used to open the icon views context menu
|
|
to avoid warning with Clang Analyzer
|
|
to avoid warning with Clang Analyzer
|
|
|
|
- caja-connect-server-dialog
- caja-navigation-window
- caja-property-browser
- caja-sidebar-title
- caja-trash-bar
- caja-window
- caja-zoom-action
- caja-zoom-control
- fm-desktop-icon-view
- fm-properties-window
|
|
An example of when the MIME type might change: a file is initially created
with 0 bytes of content, but more data is added later. Empty files are always
detected as plain text, but the file might not be empty anymore when the user
opens it.
This commit affects the behavior when double-clicking a file and when right-
clicking on it too.
|
|
The code looked like it was supposed to check whether each file in the
selection could be opened in an external app, but was only checking the
first item in the selection repeatedly.
This bug may have been mostly benign since the subsequent call to
caja_mime_get_default_application_for_files will return NULL anyway if the
files don't all match each other.
|
|
This reverts commit 021ff2ac062f1cfd52726c78e9a3956405001c6e.
Fixes https://github.com/mate-desktop/caja/issues/1101
|
|
|
|
|
|
'g_strconcat' needs to be freed
|
|
In the function initial_permission_state_consistent, when the check was
made to see if the files have the same permissions, the check was not
correct.
To fix this, also do & between the first_permissions and the mask.
https://bugzilla.gnome.org/show_bug.cgi?id=698955
Adapted from https://gitlab.gnome.org/GNOME/nautilus/commit/37595852
|
|
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
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
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
|
|
Fixes https://github.com/mate-desktop/caja/pull/956#issuecomment-377222055
|
|
avoid deprecated:
gtk_image_menu_item_new_from_stock
gtk_image_menu_item_new_with_mnemonic
gtk_image_menu_item_set_image
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
Fixes https://github.com/mate-desktop/caja/issues/698
|
|
Fixes https://github.com/mate-desktop/caja/issues/859
|