2013-06-27, 02:52
(2013-06-27, 00:38)RazorFR Wrote: Thanks a lot for this great plugin.It's normal that Advanced launcher store thumbnails images into C:\Users\Me\AppData\Roaming\XBMC\userdata\profiles\Me\addon_data\plugin.program.advanced.launcher\Thumbnails\. For files launchers, if you do not indicate thumbs and fanart paths during the launcher creation, thumbs and fanarts images are stored by default into the same direcoty than the items. For stand alone launchers thumbs and fanarts images are stored by default into C:\Users\Me\AppData\Roaming\XBMC\userdata\profiles\Me\addon_data\plugin.program.advanced.launcher, because you generally do not have the sufficient rights to save these files into the same directory than the executable (C:/Program Files) or the binary (/usr/bin) files.
I am getting an error from the latest version of the advance launcher each time I update a artwork (thumbnail or fanart).
Though despite the py. error, thumbs are correctly cached once I exit and re-enter the addon.
I looks like the addon is trying to cache artworks in the following directory:
C:\Users\Me\AppData\Roaming\XBMC\userdata\profiles\Me\addon_data\plugin.program.advanced.launcher\Thumbnails\
That's my profile folder in xbmc directory, where indeed all addon data/settings are stored.
But I only use one profile, and my thumbnails folder is still in the xbmc root folder:
C:\Users\Me\AppData\Roaming\XBMC\userdata\Thumbnails
I tried the to use path subsitution and move thumbnails to my profile folder, that does the trick, but that's probably not intended to work that way.
Or maybe I missed something in the addon settings to point at the correct thumnails folder.
Cheers
Also, thumbs and fanarts images stored by Advanced launcher are not cached images. That's XBMC who next cache them into C:\Users\Me\AppData\Roaming\XBMC\userdata\Thumbnails. But Advanced Launcher is not XBMC, and generally when you scrap images, you want them to be definitively saved, and not only temporary.
Now, concerning your error message, it is not normal, could you please port here the xbmc.log file just after the error occurs. It will help me to found what is going wrong.