Thumbnail size change is not considered by us as something that user will do frequently / regularly:
- thumbnails are generated in exact size they're displayed (to avoid sharpness loss on second resize)
- thumbnails are stored in memory (so, generating larger thumbnail for future quick resize will take a lot of extra RAM)
So, each thumbnail change results in completely dropping of memory thumbnail cache and regenerating thumbnails.
As a result, moving thumbnail size change to a hotkey (invitation for frequent resizing) requires big changes in FRV internals (and, definitely, such change will result in much more RAM used for thumbnails cache).
Dear Sir:
Dear Sir:
Thumbnail size change is not considered by us as something that user will do frequently / regularly:
- thumbnails are generated in exact size they're displayed (to avoid sharpness loss on second resize)
- thumbnails are stored in memory (so, generating larger thumbnail for future quick resize will take a lot of extra RAM)
So, each thumbnail change results in completely dropping of memory thumbnail cache and regenerating thumbnails.
As a result, moving thumbnail size change to a hotkey (invitation for frequent resizing) requires big changes in FRV internals (and, definitely, such change will result in much more RAM used for thumbnails cache).
--
Alex Tutubalin/FastRawViewer team