Age | Commit message (Collapse) | Author | Files | Lines |
|
This patch resolves three related issues:
The first issue was that the GSettings schema for Caja did not include an
entry to sort by the "btime", or creation date, of files. If the user chose
such an option in the Caja Preferences, GSettings would produce a warning
(often out-of-sight, as it was usually redirected into the user's
.xsession-errors file), and Caja would not actually change the default
sort-order of files. This patch adds the btime as a valid setting in the
schema.
The second issue was that. because of the above (an entry in the settings
schema was missing), some of the alternative sort orders listed in the schema
(everything after and including "atime") were not assigned the same numbers
as the sort orders listed elsewhere in the Caja source code. Specifically,
in icon- and compact-views, if the default sort-order was "emblems", the
observed / actual sort-order would be the entry before "emblems", namely
"atime" -- so instead of sorting by the names of associated emblems, Caja
would sort by each file's access time. An array in the code for the
list-view also was missing many values and included some values out of order,
so the default sort-order setting affected directories viewed in list-view
mode seemingly randomly. The former is taken care of using the fix described
in the above paragraph; the latter is fixed in this patch by adding /
reorganizing the array for the list-view sort-orders appropriately.
The third issue (admittedly, a lesser issue) was that the documentation for
the default-sort-order setting was lacking -- it at least did not list all
the possible values that the setting could accept. In this patch, I resolve
this issue by listing all values in the setting's description, and also go
into more detail about what each value does. (However, perhaps I included
a little too much detail. It'll only benefit [supposed power users who may
already know this stuff] who use GSettings or DConf directly, and it'll
certainly be a headache for translators. I'll admit that.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
use gtk_drag_begin_with_coordinates instead
|
|
|
|
|
|
Do not need to extend glib library, since it now incorporates these functions.
Extended date format modifiers are available on glib v2.56.
eel-glib-extensions.h/c:
GDate * eel_g_date_new_tm (struct tm *time_pieces);
char * eel_strdup_strftime (const char *format, struct tm *time_pieces);
gint64 eel_get_system_time (void);
Do not need to test the extensions in eel_self_check_glib_extensions (void).
eel-glib-extensions.c:
static void check_tm_to_g_date (time_t time)
static char * test_strftime (...)
Do not need to check if strftime implements extended date format modifiers on the system (available on glibc v2.27).
configure.ac
|
|
|
|
|
|
|
|
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
|
|
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
|
|
|
|
|
|
|
|
Fixes https://github.com/mate-desktop/caja/issues/698
|
|
this menu item is only visible when list view is selected,
so I'm not surprised we missed it
|
|
ported from:
https://git.gnome.org/browse/nautilus/commit/?id=4f17fb7db7b8736ebb4fe82ddb1c279777847730
https://git.gnome.org/browse/nautilus/commit/?id=41de4e52b43c8ed5c9118860dac7caa303ebbc5b
|
|
This reverts commit 2a424fca8bd928223e92570fa692266c471a52b3.
|
|
|
|
|
|
|
|
|
|
the file.
|
|
This is a backport from nautilus 5b09cedf434b53a975074b346d511335fc735cba
list-view: explicitly set cursor on file name cell renderer on rename
The file name column has two cell renderers, one for the icon and another for
the name string. Thus, gtk_tree_view_set_cursor() isn't enough to reliably
start editing the file name cell since it will try to edit whatever is the
currently focused cell in the column.
https://bugzilla.gnome.org/show_bug.cgi?id=656128
Fixes https://github.com/mate-desktop/caja/issues/741
|
|
|
|
fixes https://github.com/mate-desktop/caja/issues/649
adapted from:
https://git.gnome.org/browse/nautilus/commit/?id=e19f7cb3fec1e6c884d1741c3c00916c65ab035f
|
|
|
|
option
*Remove GTK_VERSION_CHECK (3, 0, 0) and libunique selectors
*Remove GTK2 and libunique specific code.
*Leaves selector for specific GTK3 versions.
*Remove #DEFINES for vbox/hbox previously required for GTK2 compatability
*Keep vbox in caja-spatial-window.c, it is necessary for the desktop to work
*spatial-window vbox issue at https://github.com/mate-desktop/caja/issues/591
|
|
Fixes https://github.com/mate-desktop/caja/issues/78
Co-Authored-By: Oliver Joos <[email protected]>
Co-Authored-By: Nelson Benitez Leon <[email protected]>
|
|
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=f81188e
|
|
|
|
|
|
gdk_cursor_new i deprecated with gtk+-3.16 and
gdk_cursor_new_for_display is available since 2.2
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=74a8f78
|
|
|
|
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
fixes https://github.com/mate-desktop/caja/issues/452
from https://github.com/GNOME/nautilus/commit/9eee9ff6ca3e93d5d363725282d8ba393a1e6d01
|
|
|
|
Closes https://github.com/mate-desktop/caja/pull/372
|
|
|
|
GCC 4.6 introduced a new warning about variables declared and initialized,
but not really used in the function body. Remove all of these occurrences
to build cleanly.
http://git.gnome.org/browse/nautilus/commit/?id=d4230de8667764e02dbb966b5d806ff78ced2fd5
|
|
including a silly mistake in caja-window where destroy function's return type
was accidently ommitted during the addition of gtk version checks.
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|