|
Hi all,
in digikam (all versions, as far as I know), resizing of the thumbnails is done after the size slider has been adjusted to a new position. I just realized that a somewhat nicer behaviour can be found in gwenview: You drag the size slider, and the size of the thumbnails is adjusted at the same time. This looks good and allows the user to choose the size he really needs, e.g. to fit some thumbnails on the screen. I realize that this kind of polishing is probably not very high on the todo list of the developers in the current stage, but will it be implemented eventually? Being no programmer, I have the impression that it can be accomplished by simply using some code from gwenview - is that right? Or are the two progams using the same algorithms/library/whatever to resize thumbnails and the present behaviour was chosen intentionally in digikam? Best regards, Gandalf _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
2008/7/26 Gandalf Lechner <[hidden email]>:
> Hi all, > > in digikam (all versions, as far as I know), resizing of the thumbnails is > done after the size slider has been adjusted to a new position. I just > realized that a somewhat nicer behaviour can be found in gwenview: You drag > the size slider, and the size of the thumbnails is adjusted at the same time. > This looks good and allows the user to choose the size he really needs, e.g. > to fit some thumbnails on the screen. > I realize that this kind of polishing is probably not very high on the todo > list of the developers in the current stage, but will it be implemented > eventually? Being no programmer, I have the impression that it can be > accomplished by simply using some code from gwenview - is that right? Or are > the two progams using the same algorithms/library/whatever to resize > thumbnails and the present behaviour was chosen intentionally in digikam? > No code is fully different. Gwenview (or f-spot) store and resize thumbs directly from memory. the large thumbs is stored in memory and is resized without to load another reduced version from thumbs cache. It's fast but it consume a huge memory to do it. To reproduce this behaviours, we need to break code everywhere in digiKam. We can do it only when we work on 0.10.2, when we port iconview to a pure Qt4 model/view implementation. Best Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
| Free forum by Nabble | Edit this page |
