View Single Post
Old 04-26-2025, 10:41 PM   #40
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,713
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Wow, I stopped trying to set it and instead just let it create itself. Then I ask the profile what cachePath it will be using and it reports the local app data instead of the roaming one, and it adds the "cache" as well. This only happens with Windows. It reports correctly on Linux and MacOS.

But we know this is not correct at all. So QtWebEngine for windows is saying its cache is one place but it is actually in another!

I will have to either hard code in the roaming bit or try to find where that path is being created simehow. This is a mess.

Tomorrow, I will try to track down where this is being set in the Windows code in QtWebEngine.
For the record, the location being reported in the debug log is the actual location (in Sigil's prefs location) where the caches are actually being created (under the cache prefix), used, and then cleaned up properly. The problem is that the directories are also being created (but unused), and orphaned in the Roaming location. The local app data location is the correct location.
DiapDealer is online now   Reply With Quote