I'd say that the only way to keep a view with that amount of thumbnails anyhow scalable is to show images on demand. Don't attempt to load all images in memory but re-use a certain set of items to show currently visible images.
I'd say that the only way to keep a view with that amount of thumbnails anyhow scalable is to show images on demand. Don't attempt to load all images in memory but re-use a certain set of items to show currently visible images.
J-P Nurmi
how do u do that exactly? I thought qt will take care of such things....
I have been using the following code...
listwidgetitem->setIconsize(QSize(50,50); //1
listwidgetitem->setIcon(QIcon("/home..../temp.jpg"); //2
how does qt store an icon? does it store the original image in RAM and scales it down when needed. or does it store the scaled down image in ram. if it is the first case then it eats up the memory.
I have been looking into FSpot photo manager. he has been loading thausands of images and the ram was just occupying < 300MB.
what do u think? if i could create a qpixmap scale it down pass that to the setIcon function and delete the original pixmap?
I heard that libexif stores thumbnails along with other info so is it better if i use it?
does anyone have ideas ?
Try to know which items are visible...
load images only in those items/labels.
When u scroll, unload the images not in view and load new images,,,
this might be tricky,,, but only thing i can think of as of now
sriluyarlagadda (15th May 2008)
Bookmarks