Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
99f8b5f25192b8593ae337efe7f49c59ff13a3f4)
|
|
Bump minimum glib version accordingly
|
|
|
|
|
|
|
|
|
|
Since we now require GTK 2.24, we can directly use
gdk_window_get_width(), gdk_window_get_height()
|
|
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=c2c4076ceb2216ff5e696b4e78aeb63e0f86c437
|
|
http://git.gnome.org/browse/nautilus/commit/?id=a5caa0e98c844a23656cafaa9b6f985dada7bc51
|
|
http://git.gnome.org/browse/nautilus/commit/?id=3a9c6cd783507cc2fbd0a838cd6710f74e7f17dd
|
|
instead of a local-to-caja setting 'show-desktop'
This key would indicate that file managers (by default Caja, but applies to
others like Thunar or ROX) should handle desktop, i.e. draw a background and
place icons there. Otherwise (when false), mate-settings-daemon will take
over drawing desktop background.
This is different from 'draw-background', which is a separate option used
only for drawing background without icons (by mate-settings-daemon).
To Caja, 'show-desktop-icons' implies 'draw-background', and so if set to
false, Caja won't (needlessly) draw the desktop.
However, if the user uses the "Background & Emblems dialog" to drop an
image-pattern/color/reset on the desktop, Caja will again draw the desktop.
For reference:
https://bugzilla.gnome.org/show_bug.cgi?id=632225
|
|
- Fixes crashes when resizing a VM window in VirtualBox.
- Adds a method to allow handling desktop reset.
|
|
|
|
close https://github.com/mate-desktop/mate-file-manager/issues/58
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|
|
mainly, in icon-dnd, in drag_begin_callback, CajaIconContainer was only declared
for GTK2. Also, replace some deprecated gdk_drawable_get(size|screen) calls, and
remove some unnecessary GDK_DRAWABLE casts.
Also, in icon-canvas-item, in draw_label_text, missed ommitting a NULL parameter
to gtk_paint_focus, for GTK3.
|
|
|
|
Bring Caja up to speed, stage1
|
|
But unlike upstream commit below, not removing include eel-art-extensions.h
from eel-gdk-pixbuf-extensions.h, as we still have functions in the latter
using eel_irect_* (from eel-art-extensions), which are still used by the
eel-debug-drawing we kept around.
http://git.gnome.org/browse/nautilus/commit/?id=7dee3226ad6b3aa1c782cc3d2969e32c5eeae3f3
|
|
Was: general: use g_list_free_full() instead of eel functions
http://git.gnome.org/browse/nautilus/commit/?id=5e669515fd7f760382e6b7aa1449734a35a2d7f4
.
Instead of g_list_free_full(), we use g_list_foreach and g_list_free() to avoid
unnecessary glib dependency bump to 2.28
|
|
It doesn't seem to do anything useful.
http://git.gnome.org/browse/nautilus/commit/?id=1cdd0b41bf9de69a93cb166636d7eccff9f5355f
|
|
http://git.gnome.org/browse/nautilus/commit/?id=d811553a4e74106efdf8bf6c91c6d29944ed6df7
canvas: use GTK_LAYOUT casts instead of going through the parent struct
http://git.gnome.org/browse/nautilus/commit/?id=2260005986d8c620669e56c4b9f2fba12e8e0625
|
|
http://git.gnome.org/browse/nautilus/commit/?id=0f8dcf2ac394121c488afdf0fecc2b7afeb673b6
|
|
http://git.gnome.org/browse/nautilus/commit/?id=b0550951f461c2033f4d1aaa4404078c7a70f220
|
|
The feature it was bringing in (shrink when the paned handle is
double-clicked) is even confusing.
http://git.gnome.org/browse/nautilus/commit/?id=1620bd8a4e4ab1760c5c518dd954a4471645ce87
|
|
This fixes the 'Name' column being too thin in list view.
http://git.gnome.org/browse/nautilus/commit/?id=33c9b6d24a60079fe6c4c1be281c76f43def6fee
|
|
removing old comment, keeping old pixmap/mask code around for GTK2
was: icon-dnd: cleanup useless code
http://git.gnome.org/browse/nautilus/commit/?id=098057414b38aeeddd3fcd81942324336628d341
|
|
http://git.gnome.org/browse/nautilus/commit/?id=f38bad2536faf497fe56c9a491ab852cb00514c0
|
|
http://git.gnome.org/browse/nautilus/commit/?id=a136af0a01c160cdfb513c531b910b49a4a62973
|
|
http://git.gnome.org/browse/nautilus/commit/?id=c6860491c432e311d585a6d92443ef821afd46d2
|
|
http://git.gnome.org/browse/nautilus/commit/?id=e56241830bfd2ca470ec2b1da53313c2230bc2b9
|
|
http://git.gnome.org/browse/nautilus/commit/?id=910191ea13e5647e1b8c793e7585530c6ae4c9b1
|
|
http://git.gnome.org/browse/nautilus/commit/?id=c5eba3314c99059aa1fff13aedcb1004966fdd55
|
|
|
|
http://git.gnome.org/browse/nautilus/commit/?id=f5192b6990cd9240d126974dd587b7b7525ae714
|
|
the ::destroy signal of GtkObject has only been moved to GtkWidget in GTK3
(after GtkObject removal): http://developer.gnome.org/gtk3/3.0/ch25s02.html
So, we use conditionals in this case, to keep working with GTK2
Original commit:
http://git.gnome.org/browse/nautilus/commit/?id=aef4cfcf93ef34a0b2d4c87b40fcec2b7a66dd06
|