XYplorer Beta Club

admin wrote: ↑12 Aug 2024 09:47 Thanks, got it.

However, everything works as it should. (Of course I had to change the hard-coded cache path to something that exists on my system.)

"Hard-Coded" the path as an attempt to correct the defect.

It appears there's are different security access rights being used during the writing of the cache which are different than when reading the cache, and, I'd guess there is an access right violation during an initial read of the thumbnail cache which is ignored. But it appears to be directly related to ACL as it works on a low security profile on my system but always fails to read the cached thumbnails on my required secured development environment.

In the next beta, you will get an error message if the cache could not be read for some reason. That should bring some light into it.

Hi Zardoz2293, you can also use the get command to determine the thumbnail cache file e get("thumbs_cache"); Run it from the address bar or "Run script". Make sure you're currently in the picture or photo folder you're having an issue with and in the desired thumbnail viewing mode and then run that command. From that you can look at the corresponding cache ini file and its keys and possibly determine if there's an issue.

admin wrote: ↑13 Aug 2024 09:55 In the next beta, you will get an error message if the cache could not be read for some reason. That should bring some light into it.

Returned from out of town. Just downloaded v26.30.203 and was looking forward to seeing the error message. However, same behavior ---
NO ERROR MESSAGE displayed.

Found the problem---

1) In an early posting on August 8th, this thread, I showed the cache thumbnail *.ini file, which shows the problem (Image below, now marked with red arrow). At the time I did not know what I was looking at or the meaning. The date/time stamp is missing. My assumption is the format "yyyy-mm-dd hh:mm:ss" (2024-08-19 01:54:46) "Mod=" algorithm is being taken from the Windows System Short Date time format as a default format. This will not work on my system as I use a "Short Date" definition which is incompatible and breaks the XY formatting algorithm. I have observed many Corporate accounts which have used the System Date Time APIs default formats in algorithms to be problematic when the timestamp format can be dynamically changed by the end-user for constraints which where not contemplated.

WHY is the "; 2024-08-08 10:07:09" at the header comment field formatted correctly but the "Mod=" is missing? Me thinks different method to output the data?


2) Perhaps the READ function should throw an error if the "Mod=" is null ?


BTW, I want to THANK YOU and EVERYONE for helping resolve. Seriously. THANK YOU!
I look forward to update.

Looks like the solution indeed.

... I use a "Short Date" definition which is incompatible and breaks the XY formatting algorithm ...

Well, what does that definition look like?

admin wrote: ↑19 Aug 2024 11:54 Looks like the solution indeed.

... I use a "Short Date" definition which is incompatible and breaks the XY formatting algorithm ...

Well, what does that definition look like?

I was bitten by this Microsoft VB6 'feature' in 1994 CE i.e., "dd MMMM yyyy - dddd" (there are others). There are more than a few VB6 functions accepting arguments which result in throwing an error or effect your expected output via a 'feature'.

Thanks! Fixed in next beta.

admin wrote: ↑19 Aug 2024 15:00 Thanks! Fixed in next beta.

Thank you Sir!

You are a true gentlemen "exotic custom definition"; myself, not having evolved to a higher state have used more colorful definitions.