summaryrefslogtreecommitdiff
path: root/libcaja-private/caja-icon-container.c
AgeCommit message (Collapse)AuthorFilesLines
2018-05-05avoid deprecated 'gtk_style_context_get_background_color'Pablo Barciela1-1/+7
2018-05-03Eliminate accessible children-changed event flood on container repopulationJoanmarie Diggs1-2/+4
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.
2018-04-24Eliminate accessible children-changed event flood during update allJoanmarie Diggs1-0/+6
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.
2018-04-24Emit accessible-name-change signal for icons only when icons are renamedJoanmarie Diggs1-0/+4
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.
2018-04-04Scale screen dimensionsVictor Kareh1-6/+12
2018-04-04canvas-container: listen to scale factor to invalidate iconsLionel Landwerlin1-0/+12
This is one of the condition that needs to trigger an invalidation to recompute layout at the correct size. https://bugzilla.gnome.org/show_bug.cgi?id=776896 origin commit: https://gitlab.gnome.org/GNOME/nautilus/commit/b257699e
2018-01-31require GTK+ 3.22 and GLib 2.50monsta1-67/+2
2017-12-16WidthOfScreen and HeightOfScreen implementationPablo Barciela1-22/+8
This commit reverts: https://github.com/mate-desktop/caja/commit/4c130e22b98bbc1a85747adac3b582e45d34514e https://github.com/mate-desktop/caja/commit/ac12e6d16f4a51b3327d013781e72cfec17f3624 https://github.com/mate-desktop/caja/commit/17b3c0ca924ffcd4bd06fded98227eba626d4f0b https://github.com/mate-desktop/caja/commit/42c8d2c3373c25d6e321be6950997c0d7ce44279 And it applies an alternative to fix the deprecated functions: gdk_screen_get_width gdk_screen_get_height gdk_screen_width gdk_screen_height
2017-08-25gtk 3.22: avoid deprecated gdk_screen_get_monitor... functions:ZenWalker1-0/+10
avoid deprecated: gdk_screen_get_monitor_geometry gdk_screen_get_monitor_at_window
2017-08-12avoid deprecated gdk_screen_width/heightZenWalker1-2/+7
2017-08-12avoid deprecated gdk_screen_get_width/heightZenWalker1-6/+15
2017-04-19Expand grid width to canvasraveit651-1/+6
Minimum of one column taken from: https://github.com/linuxmint/nemo/commit/78d4a4f https://github.com/linuxmint/nemo/commit/21ea094 fix
2017-04-13Add size_request to IconContainer to work around unncecessaryraveit651-0/+64
relayouting 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
2017-03-13eel: Avoid deprecated gdk_window_set_background functionsAlexei Sorokin1-2/+15
Fixes partially #506, fixes compiz-reloaded/compiz#40.
2017-03-13Revert "GTK3.21:fix desktop redraw"Alexei Sorokin1-7/+0
2017-01-27Rename method to reflect its altered functionalityLuke Yelavich1-4/+4
2017-01-27Replace other instances of atk_focus_tracker_notify with appropriate ↵Luke Yelavich1-5/+5
atk_set_state calls
2017-01-06remove some unused code that's also gone upstreammonsta1-14/+0
2017-01-02Fix keyboard-down wraparound on compact viewlukefromdc1-26/+22
Fix https://github.com/mate-desktop/caja/issues/671 Apply https://git.gnome.org/browse/nautilus/commit/?id=40be4b85f51fc7b192ef7421b2ede27954997cc8
2016-12-29fix indent and spacing a bitmonsta1-11/+11
2016-12-29check for stable version of GTK+3, not for development onemonsta1-3/+3
2016-11-22move to GTK+3 (>= 3.14), drop libunique, GTK+2 code, and --with-gtk build ↵lukefromdc1-757/+5
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-10-16GTK+2: use eel helper again to set adjustment valuesraveit651-0/+36
This reverts https://github.com/mate-desktop/caja/commit/1f7ab5d for gtk2 Fixes https://github.com/mate-desktop/caja/issues/659
2016-10-16support back and forward mouse buttons to navigateMartin Matuska1-0/+10
Fixes https://github.com/mate-desktop/caja/issues/78 Co-Authored-By: Oliver Joos <[email protected]> Co-Authored-By: Nelson Benitez Leon <[email protected]>
2016-10-11Fix accessible object inherritance when used with GTK 3Luke Yelavich1-0/+57
Also disable eel accessibility code that is not needed. Fixes https://github.com/mate-desktop/caja/issues/590
2016-08-04GTK3.21:fix desktop redraw (caja-icon-container.c)lukefromdc1-3/+7
2016-07-06icon-container: don't use eel helper to set adjustment valuesraveit651-15/+10
taken from: https://git.gnome.org/browse/nautilus/commit/?id=3a9c6cd
2016-07-04Gtk+-3.20 eel-canvas: use GdkSeat operationsraveit651-0/+39
Some GdkDisplay operations have been deprecated in GDK 3.20. This commit replaces the deprecated code in eel_canvas_item_grab() and eel_canvas_item_ungrab() functions with new GdkSeat operations. https://bugzilla.gnome.org/show_bug.cgi?id=762235 taken from: https://git.gnome.org/browse/nautilus/commit/?id=225f2cf
2016-07-04GTK+-3.20 caja-icon-container: use GdkSeat operationsraveit651-1/+11
Some GdkDisplay operations have been deprecated in GDK 3.20. This commit replaces the deprecated code with new GdkSeat operations. https://bugzilla.gnome.org/show_bug.cgi?id=762235 taken from: https://git.gnome.org/browse/nautilus/commit/?id=202a66f
2016-03-17icon container: don't set label colors right after widget realizemonsta1-4/+0
the background might be not yet set at this point, and when it will be set, the label colors will be properly set on a signal anyway. so let's not do the same work twice.
2016-03-17icon container: restore original font color select logicmonsta1-1/+1
that is, before 057df2dc1d8ea67b477d696ac6feea8aaf392763 the logic itself is valid, but it was somewhat broken later in a few attempts to fix the annoying font color bugs. so let's restore it.
2016-01-31GTK3 desktop: add a caja-desktop style class to the desktop canvasWolfgang Ulbrich1-0/+9
So that themes can tweak the color/background of desktop canvas items separately. taken from: https://git.gnome.org/browse/nautilus/commit/?id=8b676a6
2016-01-25GTK3: fix deprecated GtkMiscWolfgang Ulbrich1-0/+7
2016-01-18fix fg-color of dark themesWolfgang Ulbrich1-3/+2
fixes https://github.com/mate-desktop/caja/issues/81
2016-01-15GTK3 all: don't use deprecated GDK pointer methodsWolfgang Ulbrich1-0/+8
Use the new GdkDevice methods instead. taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=a816e00 https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=cdf858f
2016-01-15don't use deprecated gdk_cursor_new for both toolkit versionsWolfgang Ulbrich1-4/+6
gdk_cursor_new i deprecated with gtk+-3.16 and gdk_cursor_new_for_display is available since 2.2
2016-01-15GTK3 general: don't use gdk_cursor_unref()Wolfgang Ulbrich1-0/+4
taken from: https://git.gnome.org/browse/nautilus/commit/?id=74a8f78
2016-01-15GTK3: don't use deprecated gtk_widget_size_requestWolfgang Ulbrich1-4/+4
gtk_widget_size_request --> gtk_widget_get_preferred_size
2016-01-13GTK3 icon-container: invalidate the layout cache on style-updatedWolfgang Ulbrich1-1/+1
This way label sizes will be recomputed if e.g. DPI settings change. https://bugzilla.gnome.org/show_bug.cgi?id=578468 taken from: https://git.gnome.org/browse/nautilus/commit/?id=2f064e5
2016-01-13GTK3 icon-container: don't chain up style-updated for the desktop containerWolfgang Ulbrich1-3/+14
Chaining up resets the background to the default color, which is not what we want for the desktop container. Fixes https://github.com/mate-desktop/caja/issues/445 taken from: https://git.gnome.org/browse/nautilus/commit/?id=83a7d27
2016-01-13GTK3 icon-container: use the "rubberband" style class for the selection itemWolfgang Ulbrich1-43/+78
Instead of using a custom style property. Autor: lukefromdc same as: https://git.gnome.org/browse/nautilus/commit/?id=ca7f81e2
2016-01-13GTK3 icon-container: remove unused code caching canvas item colorsWolfgang Ulbrich1-118/+15
Caching colors in CajaIconContainer to use them in the canvas item is not needed anymore, as gtk_render_* fetches the right values directly from the style context. taken from: https://git.gnome.org/browse/nautilus/commit/?id=77eecef
2016-01-13GTK3 icon-container: remove unused style propertiesWolfgang Ulbrich1-44/+3
taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=e652eb0
2016-01-13GTK3 icon-container: hook to style_updated instead of style_setWolfgang Ulbrich1-6/+13
taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=a083fa0
2016-01-13GTK3 icon-container: fix setting the selection when renamingWolfgang Ulbrich1-1/+9
Closes: bgo #642766 taken from: https://git.gnome.org/browse/nautilus/commit/?id=a8a5b8d
2016-01-13GTK3 icon-container: fix a couple of ACTIVE -> NORMAL typosWolfgang Ulbrich1-3/+3
taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=d0d9059
2016-01-13GTK3 icon-container: remove useless theming propertiesWolfgang Ulbrich1-28/+29
taken from: https://git.gnome.org/browse/nautilus/commit/?id=e2ca42cac78cb0287a1bbb73030e7bba8b171970
2016-01-13GTK3 icon-container: plug a memory leakWolfgang Ulbrich1-1/+6
taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=f394ce8
2016-01-13GTK3 icon-container: fix rendering of text on the desktopWolfgang Ulbrich1-2/+5
taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=2e5f7a2
2016-01-13GTK3 icon-container: don't malloc() GdkRGBA colors manuallyWolfgang Ulbrich1-7/+7
As GdkRGBA might or might not use internally a different allocator, like g_slice. This should fix some memory corruption issues, thanks to Alban Browaeys for tracking down the bug. taken from: https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-0&id=4c026bf
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-01 15:11:05 +0000