Age | Commit message (Collapse) | Author | Files | Lines |
|
Apply
https://github.com/mate-desktop/caja/pull/658/commits/4b36a91af42d8efe0f594a95d28ab8448fd73b31
then fix the selectors in source files to use the boolean selectors for libunique
|
|
One selector was not updated in caja-location-bar.c to follow use or nonuse of libunique in GTK3 builds. Fixing this revealed need for a 3-way selector in one place in caja-application.c
|
|
Also disable eel accessibility code that is not needed.
Fixes https://github.com/mate-desktop/caja/issues/590
|
|
Limit session management to non-root sessions within MATE to stop restart loops in root sessions and inablity to kill off Caja in non-mate sessions such as XFCE. Also remove the autostarted hold-in previously used to stop restart loops.
egg_sm_client_set_mode only works when called before the main loop starts, thus it cannot be used in GtkApplication startup functions or otherwise later in the program.
Note that this commit restores the Caja 3.16 and earlier restart loop in normal mate sessions if a user disables icons on the desktop, then sets exit_with_last_window. The combination is the default for root/not in mate sessions though, so without the ability to set "no restart" later than the start of the main loop, session management outside of MATE and in root sessions has to be disabled.
|
|
Add --disable-libunique configuration option for GTK3 builds. This builds a port from libunique to GtkApplication. keep GTK2 builds unchanged
Caja can now be build with GTK2 and libunique, GTK3 and libunique, or GTK3 without libunique using GtkApplication instead
GtkApplication port Based on cherrypicked nautilus commits from
https://github.com/GNOME/nautilus/commit/a8481ee4bd8d34e792d63598fa5efb47736f9de4
main: adapt to GtkApplication changes
through
https://github.com/GNOME/nautilus/commit/c3382e0415d51082545f277c380d37be160e8d2d
application: move nautilus_application_new() to its own function
GTK3/GtkApplication builds: add --force-desktop option
This is useful for other DE's
All: StartupNotify=false in .desktop files, as caja never connects to notification daemons and in GtkApplication builds this causes busy spinning curors
|
|
Fix the gsignal warnings on window-close
based on https://github.com/mate-desktop/atril/commit/fda33fbeedc0aab64d9479850047d0817d0b38be
"Check if handler_id is connected before disconnect" from Atril
Also Fix "Source ID XXX was not found..." warnings on closing Caja
These three gsources are already gone when Caja exits, their ID's still exist but they cannot be found to remove. The warnings indicate double removal so this code block is just a source of errors. Leave it in place but commented out for now.
|
|
Apply https://github.com/itzexor/nemo/commit/2c60a3edaef10e9ef331740d55d3c45dd366c5db
window: remove custom get_preferred_width/height implementation
We already take care of the default size when we create the window, and these only break assumptions of the default GtkWindow's handlers.
in turn from
https://github.com/GNOME/nautilus/commit/da06dfc438e578405d616c48e8e3809d37c908bb
Nautilus commit is from Feb 17, 2014 prior to release of GTK 3.14. Could not build against GTK 3.14 over GTK 3.22 system due to mate-desktop errors but should work as Nautilus used it with 3.14. Test builds with GTK 3.16 and 3.22 worked fine, no issues with saved or command line geometry
|
|
|
|
|
|
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
|
|
Duplicate define of "CAJA_ACTION_UP_ACCEL" removed.
|
|
|
|
|
|
|
|
Apply https://gist.github.com/raveit65/51b40a20f8836562369fc155a828edc4 to add a "finalize" function to the desktop window and stop background-change crashes after turning icons off-or off and back on.
Also match tab styling to that in rest of file, the one difference here from the patchfile.
|
|
Apply Alberts Muktupāvels' https://bugzilla.gnome.org/attachment.cgi?id=332444&action=diff to Caja, it just plain works.
Remove previous fallback background code.
Add GTK 3.21 selectors missed in caja_desktop_window_class_init, clean up a couple tabs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Stop the properties window from ballooning to full screen height when built and run with GTK 3.21/22. In GTK 3.21 the "emblems" tab's scrolled window will expand to the entire height of the screen attempting to accomodate all icons unless this is explicitly limited using the new command gtk_scrolled_window_set_max_content_height().
Unfortunately that command is GTK 3.21 and later only, so this forces GTK 3.21 builds to be run only with Gtk 3.21 and later. Thus this is put behind a GTK 3.21 selector and packages built from it must depend on GTK 3.21 and later. Fortunately no distro is going to ship any file manager built with newer GTK 3 than they ship. A GTK 3.21 build of this will actually open in 3.20 but hit the undefined symbol and crash if you select "properties" on any item, exactly as I would expect it to so.
|
|
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
|
|
|
|
|
|
The bar is an horizontal box already, no need to pack another hbox in
it. This also fixes content not expanding in the available width, as
noted in https://bugzilla.gnome.org/show_bug.cgi?id=654389.
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-2&id=7596049
|
|
|
|
Merge the useful pieces into CajaLocationBar itself, which is the
only implementor anyway.
taken from:
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-6&id=ca1fa0c
https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=66c46dd
|
|
This reverts commit d866d7a3a5b778cbd413eaa67ad69c80e9277c6b.
This commit breaks desktop drawing,
revert fixes https://github.com/mate-desktop/caja/issues/591
|
|
|
|
|
|
|
|
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=ba52f92
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=f81188e
|
|
There should be no need for all these roundtrips here. We can assume
if we got an event on the notebook, it will be within a GtkNotebook.
taken from:
https://git.gnome.org/browse/nautilus/commit/src?id=bbd77ce
|
|
|
|
This reverts commit a8bbcc7f391718b7220ef7bf55b1309b254a7051.
|
|
This reverts commit f7c1b8e3bf55c5a342a217a662718044c7f34e06.
This makes the locationbar smaller. The navigationbar is something
like a container for the locationbar, so fixing here the deprecation is worse.
|
|
|