Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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.
|
|
|
|
taken from
https://git.gnome.org/browse/nautilus/commit/?id=564264cc6cc6fa44390791248019547a7133d70d
and applied in some other places as well
|
|
for example, a file named simply "%s"
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=d69885bd67edc1fae76c790f6162807817d63b2f
|
|
I hate Schroedinger's bugs...
|
|
|
|
So that themes can tweak the color/background of desktop canvas items
separately.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=8b676a6
|
|
|
|
|
|
|
|
partially taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-2&id=bd151c8
|
|
also use GtkBox type in both GTK+ builds
|
|
|
|
|
|
|
|
|
|
this completes https://github.com/mate-desktop/caja/commit/cf39567
|
|
fixes https://github.com/mate-desktop/caja/issues/81
|
|
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=67028ca
|
|
|
|
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
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=8296f8c
|
|
Since we don't ever call gdk_threads_init()
|
|
gtk_widget_size_request --> gtk_widget_get_preferred_size
|
|
Set the PangoAttributeList on the GtkLabel instead.
and 'don't force a size request on the labels'
This is not required anymore in GTK+ 3
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=52b8185
https://git.gnome.org/browse/nautilus/commit/?id=b8077a7
https://git.gnome.org/browse/nautilus/commit/?id=1457f53
|
|
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
|
|
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
|