| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Apply patch by ZenWalker for horizontal scrollwheel mice, without it
scrolling left or right scrolls right only
|
|
Apply Nautilus commit https://github.com/GNOME/nautilus/commit/0832acdb4371fc7de957303e220e899c8fdcdf5c
|
|
|
|
|
|
GTK 3.19/3.20 builds only:
Applying the .view class to the icon container no longer works in gtk3.19, so apply it to the scrolled window instead. Apply it in both icon view and compact view, as both need it. Doing it from this file prevents it from being applied to the scrolled window under a treeview, thus preventing the exposed corner above the scrollbar in a treeview from showing the view background color.
Tested this build in gtk3.19.8 with good results. Tested in my own theme (UbuntuStudio_Legacy),Adwaita, BlackMATE, Green-Submarine, and BlueMenta, all still work right. Adwaita now shows the proper white view color, and my own theme gives a white icon view without also showing
white squares over the treeview scrollbars. That was an unwanted side effect of applying the view color in the gtk theme to all the scrolled windows containing list, icon, or compact views as there is no way to tell them apart from the theme only. This approach keeps the scrolled window under the treeview transparent but themes them under icon or compact views.
Using .view rather than a custom class enables themes not written for MATE to set the Caja background to match expected view colors, just as it did on the icon container in gtk3.18 and earlier. Leave it on the icon container too, as it may be needed in some themes to theme elements within the icon view.
Also, I found no ill effects from the added style class on gtk3.18. In that case, the .view style class on the icon container should cover over anything in the scrolled window. Since the style class is not applied to the scrolled window used by a list view, no ill effect there in gtk 3.19 or gtk3.18. Applying to gtk3.19 only builds for now just in case
|
|
|
|
|
|
|
|
Bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1005660
Solution from: https://git.gnome.org/browse/nautilus/commit/src/nautilus-icon-view.c?h=gnome-3-2&id=a67212a
|
|
See https://bugzilla.redhat.com/show_bug.cgi?id=959444
|
|
Fixes issues:
https://github.com/mate-desktop/mate-file-manager/issues/120
https://github.com/mate-desktop/mate-file-manager/issues/161
|
|
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
|
|
- Fixes crashes when resizing a VM window in VirtualBox.
- Adds a method to allow handling desktop reset.
|
|
This solves issues where the audio previewer is not capable of
understanding some GVfs URIs. (#624841)
http://git.gnome.org/browse/nautilus/commit/?id=ebcbb167876f8b4491af0bc86bc29015c211b3af
|
|
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
|
|
also move the sort order prefs from view-specific to common prefs
we already only have one UI setting that controls both, so it makes
no sense to have two settings.
(from nautilus 3.0)
|
|
|
|
|
|
|
|
|
|
|
|
|
