Bug in XY thumbnail memory management

[klownboy]

Hi Don, I've been experimenting with "unthumb". It looks like it "unthumb" as you said, removes the thumbs leaving the icons, but leaves the actual <xythumbs> cache files in place (i.e., they are not deleted). Maybe that was the intent? From testing it looks like the cache files can then be deleted even when the view remains open showing the thumbs changed to icons. I was able to delete the pairs of cache files from <XYthumbs> while in pane 2 while the remaining "icon" view was up in pane 1. Thanks.

[admin]

Yes, that's how I intended it.

[klownboy]

Nice, now in a script, if someone selects folders in which to delete the thumbnail cache files and one of the folders happens to be the current folder, I can then use your "unthumb" on that folder and proceed to delete the associated cache files...much better than having to move them out of the folder especially since moving them back to the folder would automatically regenerate the thumbs.

To be clear on what it's working on...calling unthumb will "unthumb" the folder which the user is currently viewing in the list panel which in my mind is always going to be "<curpath>" as far as scripting goes.

Not a problem, but a by the way, I noticed that my "xythumbs.txt" file was wiped clean after updating and then starting making new entries as I visited image folders. It may concern some people who might notice (if they notice). My thumbnail script updates the txt file based on the actual database anyway so I didn't care.

Thanks Don

[admin]

Yes, unthumb makes sense only when thumbnails are currently showing in the active pane. (Next version will allow to apply it to the inactive pane),

Actually, part of what I said previously appears to be wrong (it was true before the major changes in XY thumbnail memory management). When you switch to a non-thumb view, the cache files are closed and can be deleted. No need to call unthumb in non-thumb views.

[klownboy]

When you switch to a non-thumb view, the cache files are closed and can be deleted

Thanks Don, it was looking that way to me be based on testing.