After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701014 - Iconview relayouts after a row change even if the row changed does not change its size
Iconview relayouts after a row change even if the row changed does not change...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkIconView
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 691448
 
 
Reported: 2013-05-25 18:06 UTC by José Aliste
Modified: 2018-04-15 00:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
[PATCH] iconview: Don't relayout after a row-change that does not change the cell size (2.83 KB, patch)
2013-05-25 18:26 UTC, José Aliste
none Details | Review

Description José Aliste 2013-05-25 18:06:59 UTC
The title says it all :). If we get a iconview with 300 items, then relayout on it will take around 50 ms in my machine...  So basically, if you just change a lot of rows very quickly, then you'll see items disapearing... and you won't be able to scroll smoothly in the Iconview. 


In our usecase, this is bad because we have a iconview with thumbnails. In order to "lazy Load" the thumbnails, we set a ListStore with a blank thumbnail for each page. Then as pages become visible or invisible, we have a worker thread that render the thumnails and then changes them in the list-store. Hence we are getting a lot of relayouts when scrolling the widget.
Comment 1 José Aliste 2013-05-25 18:26:04 UTC
Created attachment 245302 [details] [review]
[PATCH] iconview: Don't relayout after a row-change that does not change the cell size

 gtk/gtkiconview.c | 42 ++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 40 insertions(+), 2 deletions(-)
Comment 2 Matthias Clasen 2018-02-10 05:00:33 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:12:15 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new