Age | Commit message (Collapse) | Author | Files | Lines |
|
This allows icons in most places to scale up properly for HiDPI
displays.
|
|
Port the rendering of icons to cairo surfaces, so that we can apply the
GDK scale factor when rendering icons.
origin commit:
https://gitlab.gnome.org/GNOME/nautilus/commit/0d4555d7
|
|
|
|
fixes https://github.com/mate-desktop/caja/issues/779
ported from:
https://git.gnome.org/browse/nautilus/commit/?id=04116ab2876412445c788091be07d7f7321a4a94
|
|
|
|
|
|
|
|
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
|
|
Replace size request code with padding code borrowed from Nemo. For some reason gtk_widget_set_margin_start(or end) does not throw GTK warnings when called on GTK_WIDGET(button_date->label) while gtk_widget_set_size_request does throw warnings. Neither generates a build warning.
|
|
Stop the "allocating size of GtkButton <xxxx> without calling gtk_widget get preferred width/height()" warnings from caja-pathbar's slider buttons
|
|
Fix gtk_widget_create_pango_layout: assertion 'GTK_IS_WIDGET (widget)' failed warning and those descending from it. This does NOT fix the gtk_widget_set_size_request: assertion 'GTK_IS_WIDGET (widget)' failed, which occurs because recent GTK3 versions warn that button_data is not a GtkWidget but still succeed in setting the size. Since GTK 3.22 will be the LAST version of GTK3 this won't break until GTK4 if ever.
Taking this out caused the pathbar buttons to jump on bold text so it had to be retained
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/src?id=6f6bfde
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/src?id=00257f2
|
|
taken from:
https://git.gnome.org/browse/nautilus/patch/src?id=4b2753d
|
|
This will give it more horizontal spacing, like we do for text buttons
in main toolbars.
taken from:
https://git.gnome.org/browse/nautilus/commit/src?id=fe45b63
|
|
We want the down slider button to be linked visually to the rest of the
pathbar.
https://bugzilla.gnome.org/show_bug.cgi?id=680916
inspired from:
https://git.gnome.org/browse/nautilus/commit/src?id=71db3de
|
|
use instead a symbolic icon
taken from:
https://git.gnome.org/browse/nautilus/commit/src?id=25c898b
|
|
inspired from:
https://git.gnome.org/browse/nautilus/commit/src?id=d808c2d
|
|
Or we might end up with buttons having the wrong size if a folder on the
pathbar changes name.
https://bugzilla.gnome.org/show_bug.cgi?id=671865
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-6&id=7358824778
|
|
|
|
|
|
|
|
|
|
caja-pathbar.c: GtkStyleContext is already used to style the pathbar, so removed GtkStyle variables and unneeded caja_path_bar_style_set function
|
|
Needed for gtk+-3.20
|
|
Since we don't ever call gdk_threads_init()
|
|
|
|
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
|
|
Closes https://github.com/mate-desktop/caja/pull/372
|
|
|
|
|
|
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
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|
|
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=22cb1accd98c1ae10938eac10cc6beda8fb6b145
|
|
http://git.gnome.org/browse/nautilus/commit/?id=c47d18f566fa9518ca7750922da7da66d3211f3e
|
|
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 this case, to keep it working with GTK2.
A tad similar:
http://git.gnome.org/browse/nautilus/commit/?id=cc6cb51e827c0b15d4ef09f12d37b9f331ddcef8
|
|
http://git.gnome.org/browse/nautilus/commit/?id=8d07a73b28767b7c866fe403e9ac706b8affb8a2
|
|
|
|
|
|
|
|
This should fix once and for all the crashers when ejecting devices
Patch by Cosimo Cecchi <[email protected]>
http://git.gnome.org/browse/nautilus/commit/?h=gnome-2-32&id=c3b54e662b52ca15d1dcbe68386b8fa82b12adc5
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=627901
http://git.gnome.org/browse/nautilus/commit/?h=gnome-2-32&id=1dc416887bf1e88c4b49bd1ac2101e0fb8460af8
|
|
|