Large Dump = Slow Scanning

[LukeWolfGames]

Hello,

Thanks for creating CacheMonkey, it's a great little application to use.

This is an enhancement request. I understand that CacheMonkey has to check to see if the image is already in the cache so it prevents duplication, but when there are a lot of images in the cache already it can take a long time to go through each of them to see if they are a duplicate.

My idea is if it can somehow recognise the last image it downloaded before stopping then it can use that like a bookmark so it does not have to check previous images. There must be some sequence to the cache files to keep track of this somehow.

It would become very efficient at collecting new images even when the cache is big.

[AlekEagle]

This issue is very apparent on large caches upwards of 2500+ items, but this is mainly an issue with how the program renders the images, instead of rendering the images only on screen it renders all of them at once, causing slowdowns, and from my experiences, the program hanging entirely. I'm sure that there is a way to render an image when it's on screen, then unload it when it has gone off screen.