Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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
|
|
This reverts https://github.com/mate-desktop/caja/commit/1f7ab5d for gtk2
Fixes https://github.com/mate-desktop/caja/issues/659
|
|
Fixes https://github.com/mate-desktop/caja/issues/78
Co-Authored-By: Oliver Joos <[email protected]>
Co-Authored-By: Nelson Benitez Leon <[email protected]>
|
|
Also disable eel accessibility code that is not needed.
Fixes https://github.com/mate-desktop/caja/issues/590
|
|
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=3a9c6cd
|
|
Some GdkDisplay operations have been deprecated in GDK 3.20.
This commit replaces the deprecated code in eel_canvas_item_grab() and
eel_canvas_item_ungrab() functions with new GdkSeat operations.
https://bugzilla.gnome.org/show_bug.cgi?id=762235
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=225f2cf
|
|
Some GdkDisplay operations have been deprecated in GDK 3.20.
This commit replaces the deprecated code with new GdkSeat
operations.
https://bugzilla.gnome.org/show_bug.cgi?id=762235
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=202a66f
|
|
the background might be not yet set at this point, and when it will
be set, the label colors will be properly set on a signal anyway.
so let's not do the same work twice.
|
|
that is, before 057df2dc1d8ea67b477d696ac6feea8aaf392763
the logic itself is valid, but it was somewhat broken later in a few
attempts to fix the annoying font color bugs. so let's restore it.
|
|
So that themes can tweak the color/background of desktop canvas items
separately.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=8b676a6
|
|
|
|
fixes https://github.com/mate-desktop/caja/issues/81
|
|
Use the new GdkDevice methods instead.
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=a816e00
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=cdf858f
|
|
gdk_cursor_new i deprecated with gtk+-3.16 and
gdk_cursor_new_for_display is available since 2.2
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=74a8f78
|
|
gtk_widget_size_request --> gtk_widget_get_preferred_size
|
|
This way label sizes will be recomputed if e.g. DPI settings change.
https://bugzilla.gnome.org/show_bug.cgi?id=578468
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=2f064e5
|
|
Chaining up resets the background to the default color, which is not
what we want for the desktop container.
Fixes https://github.com/mate-desktop/caja/issues/445
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=83a7d27
|
|
Instead of using a custom style property.
Autor: lukefromdc
same as:
https://git.gnome.org/browse/nautilus/commit/?id=ca7f81e2
|
|
Caching colors in CajaIconContainer to use them in the canvas item
is not needed anymore, as gtk_render_* fetches the right values directly
from the style context.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=77eecef
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=e652eb0
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=a083fa0
|
|
Closes: bgo #642766
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=a8a5b8d
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=d0d9059
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=e2ca42cac78cb0287a1bbb73030e7bba8b171970
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=f394ce8
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=2e5f7a2
|
|
As GdkRGBA might or might not use internally a different allocator, like
g_slice.
This should fix some memory corruption issues, thanks to Alban Browaeys
for tracking down the bug.
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=4c026bf
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=2e5f7a23350016c67bb9e9cca86a9fb2360d79e2
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=4f23a0a
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=42865d5
|
|
fixes #438
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
icon-container: reset the double click counter after a double click
|
|
however, now it will auto-scroll to the left if you manually
scroll to the right and then click on any filename. I presume
this behavior is more desired than the previous one. if it's
not so, let me know (in the comments).
adapted from
https://github.com/linuxmint/nemo/commit/72c2214c82637ab622438d46c28e67289a49d472
(thanks to @glebihan)
fixes https://github.com/mate-desktop/caja/issues/406
|
|
If we don't do this, we ignore any other double click event that happen
during the next 'gtk-double-click-time' interval after the first double
click.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=a8539a6
|
|
Closes https://github.com/mate-desktop/caja/pull/372
|
|
|
|
|
|
|
|
|
|
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=184096f912b119edde1f538e8cdd5ea593d753ca
|
|
|
|
99f8b5f25192b8593ae337efe7f49c59ff13a3f4)
|
|
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=a5caa0e98c844a23656cafaa9b6f985dada7bc51
|
|
http://git.gnome.org/browse/nautilus/commit/?id=3a9c6cd783507cc2fbd0a838cd6710f74e7f17dd
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|