Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
g_memmove is removed in https://git.gnome.org/browse/glib/commit/?id=6e4a7fca431f53fdfd89afbe956212229cf52200
|
|
This fixes the crasher when opening properties.
|
|
Closes #178
https://github.com/mate-desktop/mate-file-manager/issues/178
I had to recover two functions previously removed in eel-glib-extensions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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=8cb07ccf2ddcf0cb8557c763f8905558d67736de
|
|
|
|
The issue that was being debugged (crashes on VM window resize) is now fixed.
|
|
By checking new mate-bg (global) "background-fade" setting key before
initiating a fade.
This is hopefully useful for those running on older hardware, as the fading
effect could delay login/startup a bit.
For reference, see:
https://bugzilla.gnome.org/show_bug.cgi?id=623174
|
|
|
|
that is, APPEARANCE_CHANGED signal.
Also, add a verbose message to know when the signal is about to be emitted,
hopefully to aid id debugging a 'BadPixmap (invalid Pixmap parameter)'
error & crash when resizing VM window in VirtualBox (4.2.4-81684 as of date).
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|
|
|
|
this fixes #49 "Gradients-support of color-drops broken since 1.2"
|
|
|
|
|
|
1. Don't use gdk_drawable_get_display (deprecated in 2.24)
2. Use GDK_PIXMAP_XDISPLAY(pixmap) directly instead of
GDK_DISPLAY_XDISPLAY(gdk_drawable_get_display(GDK_DRAWABLE (pixmap)))
3. Don't require GTK3 for stuff in GTK2.24, which we now require, and
don't use gdk_drawable_get_size at all. So, use (i/o = instead of):
gdk_window_get_width|height i/o gdk_drawable_get_size
gdk_window_get_screen i/o gdk_drawable_get_screen
gdk_window_get_visual i/o of gdk_drawable_get_visual
4. add eel_background_draw for GTK3, eel_background_expose for GTK2
This was removed in nautilus (after eel-background-box was removed):
http://git.gnome.org/browse/nautilus/commit/?id=87eb53a0701252607b494f34c677b6506f82278c
5. background: port to rendering-cleanup & cope with renamings of gnome-bg APIs
http://git.gnome.org/browse/nautilus/commit/?id=0b664aae4090704fa2e44d42f213da2cea8bd828
http://git.gnome.org/browse/nautilus/commit/?id=426079ef07d5f902911f30b0a9d7de95f3020374
6. Fix remaining issue #41: crashes w/ gdk_x_error BadPixmap when changing screen resolution
Remove eel_background_get_pixmap_and_color(), and use the pixmap/surface & color properties
in background->details directly, when needed. i.e. No more g_object/surface referencing.
And call eel_background_ensure_realized() and make_color_inactive() where appropriate.
|
|
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
|
|
http://git.gnome.org/browse/nautilus/commit/?id=00c0b9daa2053a110e17c64fb79ce4884290dc76
|
|
http://git.gnome.org/browse/nautilus/commit/?id=31dfbdc19075ddf92b4f04a2f84e3111c3fb429b
|
|
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
|
|
http://git.gnome.org/browse/nautilus/commit/?id=12c7a03bfe3c49078cb5b44ff2651eb9ce1edce4
|
|
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=407666719856127547f5c2f3f03f6a050858239a
|
|
http://git.gnome.org/browse/nautilus/commit/?id=74a0311e65f2c9fc2d03967b0607633dcb652f88
|
|
http://git.gnome.org/browse/nautilus/commit/?id=2b7659ac4fcaa8b93ad8f409e1560aaa60dcdc12
|
|
and gtk_widget_size_request() for GTK2
http://git.gnome.org/browse/nautilus/commit/?id=4963a3c9e5526ffd139b1b0b5bff18b6ea91a717
|
|
http://git.gnome.org/browse/nautilus/commit/?id=58832e54b6a4e596693527d577e4f8fa2f3e4ccf
|
|
keeping eel_gdk_draw_layout_with_drop_shadow for GTK2
http://git.gnome.org/browse/nautilus/commit/?id=d2f141f4a5435b10b43abea0822e3d0569b67886
|
|
|
|
|
|
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 eel-image-table's case, to keep working with GTK2
|
|
|
|
http://git.gnome.org/browse/nautilus/commit/?id=b5f9acb9029c015558ab678e01fc2c8dcc8c6c82
|
|
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 conditionals in this case, to keep working with GTK2
Nautilus commit message: This implies adding a 'destroy' signal to EelCanvasItem,
with similar semantics to gtk_object_destroy()
http://git.gnome.org/browse/nautilus/commit/?id=1f615321613751a5dbc84d5ef7f20edd104b8dc4
|
|
http://git.gnome.org/browse/nautilus/commit/?id=5edcd42e503623c11bf55c6afba437b3013c7f45
|