summaryrefslogtreecommitdiff
path: root/src/caja-pathbar.c
AgeCommit message (Collapse)AuthorFilesLines
2018-07-11Fix some issues found by static analysislukefromdc1-2/+0
Apply one part of https://github.com/GNOME/nautilus/commit/c039b03590c86f5142c78d616700ef7af7c8a5a8#diff-f896071d07d34e87af94a18de95e4ea2
2018-07-11pathbar: Fix crash when accessing drive rootlukefromdc1-3/+4
Apply github.com/GNOME/nautilus/commit/e759e82386f80fb214a420b789b07a194480462c pathbar: Fix crash when accessing drive root The path bar button data is not properly set up when type button type is “root”.
2018-04-12pathbar: fix random segfaults on opening mounts from Desktoplukefromdc1-14/+55
Adapt and apply these four relevent Nautilus commits, which remove the code responsible for the segfaults: *https://github.com/GNOME/nautilus/commit/e1ad3c05a6cd08c8cbf18ae53701dd742249d5fd#diff-f896071d07d34e87af94a18de95e4ea2 "pathbar: add a path-event signal" *https://github.com/GNOME/nautilus/commit/875efc324f8e91f2d157c7532fe5570c1de421c7#diff-f896071d07d34e87af94a18de95e4ea2 "pathbar: remove unused code" *https://github.com/GNOME/nautilus/commit/cfa51e6702ade6a8ca9045791773e6e10560262f "window-pane: use the path-event signal from NautilusPathBar" (now CajaPathBar) *https://github.com/GNOME/nautilus/commit/2759def4968f89c1a2370ca5b2b91af84dc4afd3 "pathbar: add a return value from path-event signal"
2018-04-06Fix warnings from HiDPI commitslukefromdc1-0/+4
*caja-pathbar: fix warning,and in the process maybe fix occasional segfaults on opening mounted volumes from the desktop *caja-icon-info: Stop gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF (pixbuf)' failed warning by handling NULL return from function finding the pixbuf caja-icon-canvas-item-c: do not use g_object_unref where it does not work Stop the g_object_unref: assertion 'G_IS_OBJECT (object)' failed warnings on closing icon views
2018-04-04HiDPI: Convert Pixbufs to Cairo SurfacesVictor Kareh1-14/+14
This allows icons in most places to scale up properly for HiDPI displays.
2018-04-04Support HiDpi iconsCosimo Cecchi1-7/+16
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
2018-01-31require GTK+ 3.22 and GLib 2.50monsta1-8/+0
2017-08-25pathbar: enable mousewheel scrolling like it was with GTK+2monsta1-0/+5
fixes https://github.com/mate-desktop/caja/issues/779 ported from: https://git.gnome.org/browse/nautilus/commit/?id=04116ab2876412445c788091be07d7f7321a4a94
2017-06-21Fix off-by-one error in caja-pathbar.cnokangaroo1-1/+3
2017-01-06remove some unused code that's also gone upstreammonsta1-101/+1
2016-12-29fix indent and spacing a bitmonsta1-2/+2
2016-11-22move to GTK+3 (>= 3.14), drop libunique, GTK+2 code, and --with-gtk build ↵lukefromdc1-253/+19
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
2016-09-06GTK3: Fix last pathbar warninglukefromdc1-27/+18
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.
2016-09-05GTK3: Fix pathbar "w/o calling gtk_widget get preferred width" warningslukefromdc1-3/+12
Stop the "allocating size of GtkButton <xxxx> without calling gtk_widget get preferred width/height()" warnings from caja-pathbar's slider buttons
2016-09-05GTK3: fix pathbar pango warningslukefromdc1-1/+9
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
2016-07-14GTK+-3 pathbar: always show the slidersraveit651-2/+2
taken from: https://git.gnome.org/browse/nautilus/commit/src?id=6f6bfde
2016-07-14GTK+-3 pathbar: add slider-button class to slidersraveit651-0/+4
taken from: https://git.gnome.org/browse/nautilus/commit/src?id=00257f2
2016-07-14GTK+-3 pathpar: add image-button class to iconic buttonsraveit651-0/+8
taken from: https://git.gnome.org/browse/nautilus/patch/src?id=4b2753d
2016-07-14GTK+-3 pathbar: use text-button style class for pathbar buttonsraveit651-0/+4
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
2016-07-14GTK+-3 pathbar: fix allocation offset for the down slider buttonraveit651-3/+2
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
2016-07-14GTK+-3 pathbar: do not use deprecated gtk_arrow_newraveit651-7/+26
use instead a symbolic icon taken from: https://git.gnome.org/browse/nautilus/commit/src?id=25c898b
2016-07-14GTK+-3 pathbar: do not use deprecated gtk_alignment_newraveit651-7/+5
inspired from: https://git.gnome.org/browse/nautilus/commit/src?id=d808c2d
2016-07-14GTK+-3 pathbar: refresh label size request every time it changesraveit651-15/+34
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
2016-06-15GTK+-3.20: do not use deprecated gtk_button_set_focus_on_clickraveit651-0/+8
2016-06-15GTK+3 pathbar: Do not use deprecate composite-child APIraveit651-0/+8
2016-05-31GTK+2: fix build errors after last commitsmonsta1-1/+1
2016-05-30GTK+3 sidebars and caja-places: port style_set to style_updatedraveit651-9/+17
2016-05-28GTK3:caja-pathbar remove GtkStyle varslukefromdc1-2/+10
caja-pathbar.c: GtkStyleContext is already used to style the pathbar, so removed GtkStyle variables and unneeded caja_path_bar_style_set function
2016-02-02GTK3 BlueMenta: add caja-pathbar style classWolfgang Ulbrich1-0/+6
Needed for gtk+-3.20
2016-01-15GTK3: don't use deprecated gdk_threads_{enter/leave} ()Wolfgang Ulbrich1-1/+4
Since we don't ever call gdk_threads_init()
2015-12-25pathbar: remove unneeded assertsmonsta1-2/+5
2015-10-19GTK3: Replace gtk_{v,h}box new with gtk_box_newraveit651-0/+4
- gtk_{v,h}box usage is deprecated since gtk+-3.2.0
2015-01-13drop support for GLib < 2.36Monsta1-2/+0
Closes https://github.com/mate-desktop/caja/pull/372
2014-02-20Fixed crash in caja-pathbar.c (issue #209)Zaffy1-1/+1
2013-07-25Fixes for GTK3 supportStefano Karapetsas1-2/+2
2012-12-22[all] silence warnings from GCC 4.6Jasmine Hassan1-12/+0
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
2012-11-23[all] include src/glibcompat.h & use g_list_free_full() where neededJasmine Hassan1-2/+3
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
2012-11-16[all] use g_list_free() and g_strcmp0 instead of eel functionsJasmine Hassan1-6/+3
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
2012-11-16[pathbar] don't use deprecated size_request vfuncJasmine Hassan1-13/+186
http://git.gnome.org/browse/nautilus/commit/?id=22cb1accd98c1ae10938eac10cc6beda8fb6b145
2012-11-16[src] use gtk_widget_get_preferred_size()Jasmine Hassan1-9/+18
http://git.gnome.org/browse/nautilus/commit/?id=c47d18f566fa9518ca7750922da7da66d3211f3e
2012-11-16[src] don't use GtkObject (GTK3)Jasmine Hassan1-4/+2
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
2012-11-16[build] don't include marshals we don't ownJasmine Hassan1-1/+0
http://git.gnome.org/browse/nautilus/commit/?id=8d07a73b28767b7c866fe403e9ac706b8affb8a2
2012-09-05remove latest mateconf stuffStefano Karapetsas1-1/+0
2012-09-05start migration to gsettingsStefano Karapetsas1-4/+6
2012-08-12Fixed incorrect fsf addresses. Closes #28.Steve Zesch1-2/+2
2012-01-05pathbar: remove buttons only if the gone file is below the currentStefano Karapetsas1-4/+7
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
2012-01-05pathbar: fix crasher when unmounting volumesStefano Karapetsas1-8/+14
https://bugzilla.gnome.org/show_bug.cgi?id=627901 http://git.gnome.org/browse/nautilus/commit/?h=gnome-2-32&id=1dc416887bf1e88c4b49bd1ac2101e0fb8460af8
2011-12-01moving from https://github.com/perberos/mate-desktop-environmentPerberos1-0/+2165
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-23 03:11:51 +0000