J
Joe Laughlin
I'm not sure if I'm asking too much of Gtk::ListView, or if my
implementation is slowing things down...
I have a Gtk::ListStore. The first column in the model is an object that
contains about twenty attributes. I then create a Gtk::TreeView that has
one column per attribute in the object (so, around 20 attributes). I use a
cell data rendering function to connect each treeview column to each
attribute in the object.
Each object in the ListStore is updated with new data every X number of
seconds (five, for example).
It works fine if I have a pretty low amount of objects in the ListStore.
But if I put 400 objects in the ListStore and all are displayed in the
TreeView, when updates are applied to the objects, there's a noticable delay
for when the changes are displayed in the TreeView.
Am I approaching the limits of Ruby/Gtk here, or is something else that I'm
doing probably inefficient? I would greatly appreciate any suggestions
anyone has.
Thanks,
Joe Laughlin
implementation is slowing things down...
I have a Gtk::ListStore. The first column in the model is an object that
contains about twenty attributes. I then create a Gtk::TreeView that has
one column per attribute in the object (so, around 20 attributes). I use a
cell data rendering function to connect each treeview column to each
attribute in the object.
Each object in the ListStore is updated with new data every X number of
seconds (five, for example).
It works fine if I have a pretty low amount of objects in the ListStore.
But if I put 400 objects in the ListStore and all are displayed in the
TreeView, when updates are applied to the objects, there's a noticable delay
for when the changes are displayed in the TreeView.
Am I approaching the limits of Ruby/Gtk here, or is something else that I'm
doing probably inefficient? I would greatly appreciate any suggestions
anyone has.
Thanks,
Joe Laughlin