Age | Commit message (Collapse) | Author | Files | Lines |
|
When drawing the canvas item elements, don't override the parent
container style flags, so we don't lose e.g. backdrop information.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=31dad6f
|
|
Fixes a regression introduced in commit
3a858857fff5e1d7e0bffcec63fea6d2a933ce27 that causes unwanted text to be
drawn while renaming a file in icon view.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=f07aa75
|
|
And add a style class for it.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=7732a6b
https://git.gnome.org/browse/nautilus/commit/?id=2cb91c0
|
|
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
|
|
Instead of hardcoding colors and using direct cairo calls to draw the
canvas items frame/background/labels, use gtk_render_* methods directly.
This has the advantage of making them more friendly with GTK+ themes
(by adding a caja-canvas-item style class to the canvas context when drawing)
and removes a ton of convolut
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=95910c9
|
|
This fixes icons on the desktop appearing weird
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=6a11ecd
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=09f0b79
|
|
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
|
|
Instead of passing eel_pixbuf_render() always the same values
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=a1fa4ea
|
|
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=5d811bb
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=18e3369
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=0668960
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=705d814
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=f8bdf9c
|
|
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=fc74332
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=5da941e
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=7bd06fa
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=42865d5
|
|
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=83a83e3
|
|
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
|
|
fixes #438
|
|
|
|
|
|
|
|
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
|
|
|
|
fixes https://github.com/mate-desktop/caja/issues/361
|
|
|
|
* Bump intltool required version for gsettings support
* Extract strings with intltool directly
|
|
|
|
- first, we must not free the list of extensions at this point
- second, the call did nothing as the argument is NULL after
exiting the for loop
|
|
|
|
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
|
|
|