summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2022-07-22Fix build warning -Wmissing-field-initializersrbuj21-20/+47
2022-07-22Fix build warning -Wbad-function-castrbuj6-22/+43
2022-06-08Document and fix default-sort-order preferenceGordon Norman Squash2-7/+36
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.)
2022-06-08caja-file-conflict-dialog: Move to automatic signal disconnectionColomban Wendling1-20/+11
Instead of manually keeping tabs on the signals so we can disconnect them before the data parameter gets destroyed, let GObject automatically track lifetime of the data, which it can do as that data is a GObject itself. This does not change behavior in the normal case, but makes sure the callback simply cannot get called with invalid/freed parameters, even if we did screw anything up (which we used to). This actually would have solved #1630 as well with using the target widgets as data parameters as the signal would have been disconnected as soon as the widget got destroyed, no matter whether we got finalized ourselves or not. The signal IDs were also use as guards to whether the monitor was set up for the related files, but we can just as well use the state of the file list ready handle which should only be NULL when we actually have monitors set up. Even if it wasn't the case, worse case scenario would be removing a non-existent monitor, which is perfectly OK anyway.
2022-06-08caja-file-conflict-dialog: Properly release references on dispose()Colomban Wendling1-6/+19
Fixes #1630.
2022-06-08caja-file-conflict-dialog: update the icons oncerbuj1-16/+9
2022-06-01build: Cleanup long deprecated macros usageColomban Wendling1-8/+7
2022-06-01Properly initialize IconKey::scaleColomban Wendling1-0/+1
This value is used to look up icons in the cache, but somehow was not properly initialized.
2022-03-23caja-bookmark: Fix build warning -Wlogical-not-parenthesesrbuj1-1/+1
2022-03-23caja-application: Variable is assigned a value that is never usedrbuj1-2/+1
2022-03-22caja-bookmark: fix memory leakrbuj1-0/+4
2022-03-22caja-bookmark: drop create_image_cairo_for_bookmarkrbuj1-24/+10
2022-02-09Fix implicit conversion changes signedness: 'gboolean' to 'guint'rbuj10-57/+57
2022-02-09Fix some -Wsign-compare warningsrbuj16-63/+75
2022-02-09caja-file-operations: overlapping comparisons always evaluate to truerbuj1-1/+1
2022-02-08remove '-' from a m4_defineMatija Skala1-3/+3
it was not handled correctly
2022-01-30CI: Drop -Wunused-parameter for debian buildraveit651-1/+1
2022-01-30eel-editable-label: remove unused method get_font_descriptionrbuj2-10/+0
2022-01-30eel-editable-label: drop eel_editable_label_clear_layoutrbuj1-20/+7
2022-01-28caja-property-browser: 'gdk_color_parse' is deprecatedrbuj1-13/+13
2022-01-28caja-property-browser: Fix build warning -Wconstant-conversionrbuj1-9/+11
2021-12-31caja-module: fix memory leakrbuj1-1/+4
2021-12-31caja-sidebar-title: fix memory leakrbuj1-1/+5
2021-12-31fm-directory-view: fix memory leakrbuj1-1/+5
2021-12-31eel-background: fix memory leakrbuj1-4/+10
2021-12-21caja-application: avoid SEGV when profiling/debugging coderbuj1-2/+1
2021-12-19Use gresources for ui filesrbuj10-18/+41
2021-12-19caja-mime-actions: fix memory leakrbuj1-2/+9
2021-11-20Remove whitespaces before #define, #if, and #endifrbuj2-12/+12
2021-11-20Use a blank line at mostrbuj176-709/+0
2021-11-11caja-file: Remove unreachable coderbuj1-1/+0
2021-11-08caja-places-sidebar: fix right-click menu heightBenjamin Heiniger1-7/+18
* caja-places-sidebar: fix right-click menu height - prevent error and right-click menu from appearing when clicking empty area
2021-11-08caja-dnd: wrong type field in printf format stringrbuj1-1/+1
2021-10-11Fix Caja does not show icons of application launchersmouse1-1/+1
in /usr/share/applications and asks user for confirmation on launch of desktop-files here
2021-08-04release 1.26.0v1.26.0raveit652-33/+38
2021-08-04tx: sync with transifexraveit65119-11319/+10878
2021-08-04travis-Ci: use libera.chat as notification serverraveit651-1/+1
2021-08-04tx: update resourceraveit651-92/+92
2021-06-18Update copyright to 2021raveit6516-2/+16
2021-05-29release 1.25.3v1.25.3raveit652-4/+40
2021-05-29tx: pull from transifexraveit65119-102455/+106626
2021-05-29tx: update resourceraveit651-90/+86
2021-05-29travis-ci: use ubuntu focal as host systemraveit651-1/+1
fixes build issues with fedora:latest (f34) tag.
2021-05-19caja-directory.c: Fix memory leak.Michael Webster1-1/+1
When creating a new file (using a template, for instance), file-> details->is_added could potentially be FALSE, and cause this file to not be finalized along with other files if the view directory is destroyed. This can cause issues when re-entering that directory, with the file being in an undefined state, and could prevent the view from fully loading the location (this is identical behavior to that described in https://github.com/mate-desktop/python-caja/pull/64. To reproduce: - Create an svg file and save in ~/Templates. - Right-click, Create document-> svg file, name it whatever. - Navigate out of the folder. - Modify the file in a visible manner. - Re-enter the folder, note that it never finishes loading. Ref: https://github.com/linuxmint/nemo/issues/2736
2021-05-08caja-bookmarks-window.ui: expand child widgets, sane default sizembkma1-7/+18
use attribute "bold" instead of markup
2021-05-05caja-bookmarks-window.ui: remove deprecated GtkAlignment, remove empty labelsmbkma1-172/+82
2021-05-05caja-file-management-properties.ui: remove deprecated GtkAlignment (usembkma1-1219/+1157
margin-property instead), reduce default size
2021-04-26update resource for transifexrbuj1-843/+879
2021-04-22travis: disable travis builds for ubunturaveit651-1/+1
Sadly, there is a limit for free builds at docker.com See discussion https://github.com/orgs/mate-desktop/teams/core-team/discussions/25
2021-04-20Add creation time supportrbuj10-3/+75