klownboy wrote: ↑30 Mar 2022 16:15
You may be asking for trouble if you were to try and combine search results, branch, and normal folder thumbnails caches for the same folder.
Why? One cached entry per file. Makes sense to me.
klownboy wrote: ↑30 Mar 2022 16:15
As mentioned, search results are not necessarily cached unless you have that option checked in Configuration.
Regardless of caching thumbs
from a search result, it shouldn't be a problem to pull the existing image's already-generated thumb from its absolute path cache instead of regenerating one when it already exists.
klownboy wrote: ↑30 Mar 2022 16:15
If you do cache search result, would the user necessarily want those results tied to a normal cached thumbnail folder?
Yes. It makes perfect sense to me to cache the result based on the file's absolute path, not on whether the search bar contains an arbitrary search pattern or branch view. The file is always the file, it isn't going to mutate just because it's being viewed as the result of a search. 1 file = 1 cache entry
klownboy wrote: ↑30 Mar 2022 16:15
Search results change, the user may want to delete search results but not the normal folder cache etc.
This is already a problem that exists though. Move or delete a file in windows explorer that has a cached thumbnail, and presumably Xyplorer leaves the stray thumbnail around forever unless some sort of manual cleanup process is initiated. Users can accept this as a expected limitation, as the alternative would mean frequent automatic scanning for missing files, which is typically not ideal. Whether a search result changes or is initiated from a different parent folder should be of no consequence to the file itself, however. Only if the file itself is changed should the issue of its cache come into play, and this is independant of any search results.
klownboy wrote: ↑30 Mar 2022 16:15
I can just see it being a headache.
It's a headache having infinite thumbnails generated per image based on arbitrary search patterns when a cached thumb already exists. Grinding my CPU to a halt regenerating 100s of thumbnalis that are
already cached on my disk every time I press F3 is a headache. The current behavior leads to redundant file bloat, increased CPU time, and just seems logically wrong.
admin wrote: ↑30 Mar 2022 11:28
Yes, it has been designed that way for many years. I know what you mean, but currently I have no plans to change a well oiled and running system.
Ok, too bad.