Age | Commit message (Collapse) | Author | Files | Lines |
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=ca9f8d8
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=e3feaf8
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=caa55b7
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=b5302eb
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=1d3dd96
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=020adaf
|
|
There are still some rendering artifacts, but we will fix them later. (maybe)
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=d6e07c7
|
|
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=f0691e7
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=42e7268
|
|
|
|
|
|
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
|
|
adapted from https://github.com/linuxmint/nemo/commit/d5377cfd53034b6ab5588376322126f48782ec59
(thanks to @mtwebster and nautilus developer who did the original commit)
fixes https://github.com/mate-desktop/caja/issues/376
|
|
this fixes non selected text if renaming a file
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=d2c3410
|
|
Closes https://github.com/mate-desktop/caja/pull/372
|
|
Closes https://github.com/mate-desktop/caja/pull/370
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|