Age | Commit message (Collapse) | Author | Files | Lines |
|
The GtkScrolledWindow uses the widget prefered size as a guess as to
whether scrollbars are needed or not in the automatic scrollbars case.
If we don't report anything for them we typically get it wrong and cause
two size allocate calls on the child each time, with different sizes.
This (the two sizes speicifically) will cause unnecessary relayouts of
the window.
So, we just report the current size of the layed out icons as the prefered
size. This is somewhat wrong as its depending on previous size_allocation
calls rather than the "ideal" size of the widget, but since the ideal size
is ignored anyway and just used for this it works well.
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=fa6e447
|
|
taken from:
https://git.gnome.org/browse/nautilus/commit/?id=308f4ce
|
|
|
|
|
|
Fixes #752
|
|
|
|
needed after dc510d875ae166dd814cebc060186b4042b0ef30
|
|
This is a backport from nautilus 5b09cedf434b53a975074b346d511335fc735cba
list-view: explicitly set cursor on file name cell renderer on rename
The file name column has two cell renderers, one for the icon and another for
the name string. Thus, gtk_tree_view_set_cursor() isn't enough to reliably
start editing the file name cell since it will try to edit whatever is the
currently focused cell in the column.
https://bugzilla.gnome.org/show_bug.cgi?id=656128
Fixes https://github.com/mate-desktop/caja/issues/741
|
|
port of 52a3d30957889eb37e65e9c4416dbe0ea79a109c + 45f862c6178358e73470296e5793b10c486926c1 to mixed GTK+2/3 code
|
|
|
|
|
|
|
|
port of 9b62a56cbed4ffc7a1a014cf15f1e0ed767cd928 to mixed GTK+2/3 code
|
|
squashed b2c2794dc0fbefc1a2dd902a0266afe68db7f79a + cea24ed35ad7f5a22298fe6d921e30a34476ad11
|
|
property changes
|
|
|
|
fixes https://github.com/mate-desktop/caja/issues/649
adapted from:
https://git.gnome.org/browse/nautilus/commit/?id=e19f7cb3fec1e6c884d1741c3c00916c65ab035f
|
|
Fix https://github.com/mate-desktop/caja/issues/671
Apply https://git.gnome.org/browse/nautilus/commit/?id=40be4b85f51fc7b192ef7421b2ede27954997cc8
|
|
and it comes to rest on a new folder displayed in the same icon
position. Note that this is only in single click navigation, as
double clicking always reverts the cursor to the arrow
Same as GNOME/nautilus commit
https://git.gnome.org/browse/nautilus/commit/?id=d486af277f491ff5cfcfa254ebce618cd41a3edb
|
|
On this mode, after opening a folder, the hand cursor was used until the user
moved the cursor over a file or folder.
Based on Nautilus commit
https://git.gnome.org/browse/nautilus/commit/?id=2644c6ef4e7839e976d4861d6c86e16e34d46a13
|
|
|
|
This makes the string exposed to ATK more sensible, instead of having
unrelated words coupled together.
|
|
|
|
|
|
with patch by ZenWalker to fix horizontal wheel scrolling
cherry-picked and squashed from:
https://github.com/mate-desktop/caja/commit/f34590dd7a71251515b90cd9812878b7d26d30b6
https://github.com/mate-desktop/caja/commit/ae053dbf2cc26ae74df5e782261c3a3bc7126763
https://github.com/mate-desktop/caja/commit/3e93f938000cdb24a6137daecd77fe010ae93f36
|
|
As in Nautilus, use g_hash_table_new rather than eel_g_hash_table_new_free_at_exit
|
|
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.
|
|
Fix CajaIconCanvasItemAccessible inheritance to properly inherit from
EelCanvasItemAccessible. This fixes the ATK state machinery in
CajaIconCanvasItemAccessible, and adds AtkComponent support which
provides several useful features.
See also https://bugzilla.gnome.org/show_bug.cgi?id=677509 and
https://github.com/mate-desktop/caja/issues/706.
Partly based off https://git.gnome.org/browse/nautilus/commit/?id=6c5baeb7626eda6629fc6642c9eb513ef8bc5c8e
|
|
|
|
inspired from:
https://github.com/linuxmint/nemo/commit/8242e27
|
|
Only those which match application/x-desktop directly.
Apply Nautilus commit
https://github.com/GNOME/nautilus/commit/b241fd28913e87fe01419e4922259949a11c973f
|
|
|
|
Apply https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=b9c51fd4eb84a9f52ee4be1bf183fc516984130b
via
https://gist.github.com/raveit65/19cfc5fe706ac6a2ea5d663a94fb02af
|
|
Fixes https://github.com/mate-desktop/caja/issues/688
*Split caja.css. Much of it can load with GTK_STYLE_PROVIDER_PRIORITY_THEME to allow themes that support Caja to set their own style. CSS required for the desktop background to show and to keep the white text suitable for most backgrounds needs GTK_STYLE_PROVIDER_PRIORITY_APPLICATION so it is loaded separately from new file caja-desktop.css
*Move all css items that must not be overridden by themes (most of them are for the desktop) to caja-desktop.css and keep those that are only needed when themes do not set them at all in caja.css
|
|
|
|
|
|
Also disable eel accessibility code that is not needed.
Fixes https://github.com/mate-desktop/caja/issues/590
|
|
|
|
This reverts https://github.com/mate-desktop/caja/commit/1f7ab5d for gtk2
Fixes https://github.com/mate-desktop/caja/issues/659
|
|
This reverts https://github.com/mate-desktop/caja/commit/f02d495 for gtk2
fixes https://github.com/mate-desktop/caja/issues/659
|
|
|
|
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
|