| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
These preferences are all applied elsewhere and all work without this. Removing it stops the g_hash_table_foreach warnings with GTK 3.23.0
|
|
The string returned by eel_bg_get_desktop_color() needs to be freed by
the caller, which wasn't happening before.
Commit b9cf3667 fixed the case where this function was being called
repeatedly, triggering this leak and causing it to rapidly fill system
memory.
|
|
and avoid deprecated 'gtk_widget_override_background_color'
|
|
|
|
|
|
"menus-have-icons" set
|
|
|
|
Fixes https://github.com/mate-desktop/caja/pull/1004#issuecomment-398140812
|
|
|
|
|
|
|
|
Screen readers need to distinguish between the desktop window and normal
windows, to be able to provide nicer speech synthesis.
This can be done by simply adding an "is-desktop" attribute to the
underlying AtkObject.
This is here done by introducing a thin caja_desktop_window_accessible_class
class which is based on GtkWindowAccessible and just appends the
attribute.
Closes: #999
|
|
Fixes https://github.com/mate-desktop/caja/pull/1005#issuecomment-394805519
|
|
|
|
|
|
Fixes https://github.com/mate-desktop/caja/pull/1001#issuecomment-394072477
|
|
Fixes https://github.com/mate-desktop/caja/pull/962#issuecomment-389114129
|
|
|
|
|
|
|
|
Fix https://github.com/mate-desktop/caja/issues/996
|
|
drop "Input Methods"
|
|
|
|
not needed after ddf6f38db4e842abecd4f2ee77012050822b3775
|
|
follow-up to ddf6f38db4e842abecd4f2ee77012050822b3775
|
|
|
|
|
|
|
|
in favor of constant using of gtk_menu_popup_at_widget
for mouse and keyboard events.
|
|
Replace deprecated gtk_menu_popup in eel-editable-label,caja-dnd, emblem-sidebar,caja-side-pane, fm-tree-view, caja-navigation-window-pane, and caja-zoom-control
|
|
replace
gdk_error_trap_push
gdk_error_trap_pop_ignored
|
|
|
|
|
|
fixes this warning:
caja-undostack-manager.c: In function 'retrieve_files_to_restore':
caja-undostack-manager.c:1967:38: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses]
if (!(g_hash_table_size (trashed)) > 0) {
^
caja-undostack-manager.c:1967:7: note: add parentheses around left hand side expression to silence this warning
if (!(g_hash_table_size (trashed)) > 0) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
( )
|
|
|
|
|
|
|
|
|
|
When the icon container is repopulated (e.g. when using back/forward)
finish_adding_new_icons is called leading to an accessible children-
changed event flood. We can distinguish these unwanted notifications
from desired notifications by comparing the number of new icons to add
with the size of the container's icon set.
|
|
Accessible children-changed events should only be emitted when a user-
triggered action (creation of file, copying an item) causes an item to
be added.
Set container->details->is_loading (which does not seem to be used
anywhere) in caja_icon_container_request_update_all because if the
entire container is being updated, children-changed events should not
be emitted for each updated icon.
|
|
caja_icon_canvas_item_set_property was emitting accessible-name-change
signals whenever the PROP_EDITABLE_TEXT was being set for an icon. This
method is called by caja_icon_container_request_update_all when the icon
view is first loaded. Thus irrelevant events are being emitted (the name
of each icon didn't change, as far as the user is concerned). Furthermore,
this floods assistive technologies any time the user opens a folder with
a large number of files.
Moving the notification out of caja_icon_canvas_item_set_property and
into end_renaming_mode (where ICON_TEXT_CHANGED is also emitted) solves
the problem of floods of irrelevant notifications while still emitting
the signal when the name actually changes.
|
|
"gio open" from libglib2.0-bin.
|
|
|
|
|
|
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"
|
|
This was introduced in commit b28445b3d2c42a7d2dbac97983d007e4ab58684d
but has never been added to some parts of the UI.
|
|
|
|
|
|
The basenames of files are split by dots and then starting from the end
each segment is compared to find a sort order. Example:
bar.tar.bz2
foo.tar.bz2
a.bar.gz
x.tar.gz
z.tar.gz
test.tex
A heuristic determines what extension segments are part of the
extension. There is probably no perfect solution but there are much
less false positives. As a result the sorting is more intuitive and the
displayed column in the list view is better readable and displays
extensions more accurately.
In addition a bug related to the default sort criteria in the
preferences has been fixed.
|
|
|
