2010-09-02, 00:00
by jmarshall some days ago:
First issue: The "cached version of the poster" that is displayed first is likely the cached folder thumb. Check the Aeon skin code to see what it's doing - there'll be 2 image controls on top of each other. You should be able to get rid of it by (re)setting the poster via GetThumb.
Second issue: It is _completely_ unsupported that skins such as Aeon do this. Nor will it be supported. It relies on filesystem structure being a certain way which means it doesn't work in cases where the filesystem structure isn't that way. This is something we do not support. Skins can ofcourse choose to do it if they like, but if it breaks, too bad.
In the future we'll be looking at improving the way all images are cached (eg introducing mipmapping and the like, and/or possibly multiple sized images being cached) but it's not going to be for quite a while.
Cheers,
Jonathan
so I think there is a point to use it (at least at the moment, although that´s something xbmc doesn not support)
First issue: The "cached version of the poster" that is displayed first is likely the cached folder thumb. Check the Aeon skin code to see what it's doing - there'll be 2 image controls on top of each other. You should be able to get rid of it by (re)setting the poster via GetThumb.
Second issue: It is _completely_ unsupported that skins such as Aeon do this. Nor will it be supported. It relies on filesystem structure being a certain way which means it doesn't work in cases where the filesystem structure isn't that way. This is something we do not support. Skins can ofcourse choose to do it if they like, but if it breaks, too bad.
In the future we'll be looking at improving the way all images are cached (eg introducing mipmapping and the like, and/or possibly multiple sized images being cached) but it's not going to be for quite a while.
Cheers,
Jonathan
so I think there is a point to use it (at least at the moment, although that´s something xbmc doesn not support)