Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
Fixes #1630.
|
|
|
|
|
|
Hardcode scale factor to 1 in caja_file_get_icon_pixbuf functions in caja-file-conflict as these icons are already getting scaled elsewhere. Otherwise they get scaled twice and the whole dialog is ballooned oversize on hidpi
*Based on similar change made in Nautilus as a small part of fd01842f996b7d07baf2aafb0f68308fc5ed2055 "file-conflict-dialog: separate file logic from UI management " which was a more general refactoring of the file conflict dialog and split out the frontend and backend code.
|
|
find . -regextype posix-extended -regex '.*\.(c|h|ac|txt|xml)' -exec sed --in-place 's/[[:space:]]\+$//' {} \+
|
|
|
|
|
|
|
|
|
|
Changed CajaFileConflictDialog and CajaFile
|
|
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
|
|
|
|
|
|
|
|
|
|
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
|
|
based on nautilus commit:
https://git.gnome.org/browse/nautilus/commit/?id=b370817
Fixes partially #535
|
|
GtkAlignment has been deprecated since GTK+ 3.14 and the use of
halign, valign and margin properties is encouraged.
This commit aligns widgets by use of said properties instead of the
GtkAlignment widget.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=470235f
|
|
|
|
|
|
|
|
Set the PangoAttributeList on the GtkLabel instead.
and 'don't force a size request on the labels'
This is not required anymore in GTK+ 3
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=52b8185
https://git.gnome.org/browse/nautilus/commit/?id=b8077a7
https://git.gnome.org/browse/nautilus/commit/?id=1457f53
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=5da941e
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=392359d
|
|
It adds nothing and makes the text harder to read.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=d064618
|
|
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
|
|
|
|
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
|
|
http://git.gnome.org/browse/nautilus/commit/?id=73e2941f9b837d5d0326e6e88caa7a1e3fdcabeb
|
|
|
|
|
|
|