[phil65]

sorry, won´t do that. Directly accessing the disc is something I am very careful with. Skins shouldnt do that IMO because for example it can make NAS drives wake up.
The user should make sure that all wanted artwork is in the database.

phil65,

I would have though you need your NAS to wake up anyway, as you are looking for information on a listitem, thus you are about to play something. But I also understand you reasoning on this as well, so fair enough.

Another suggestion if I may.

It would be nice to be able to call a number of dialogs from within the skin. For example while we can code a custom version of a selection dialog or a yes/no dialog, we have already coded one of these, so why do we need to code it all over again? If I could provide two options to display and have the script return a result with either one of those options or a code to say that the user exited the dialog without choosing an option that would save recoding a yes/no dialog for each instance of a yes/no that I wanted to use.

Finally, love the blur idea. As to Ronie's post about Android not having a working PIL library, could you not just return the image unchanged if you can't find PIL. That way most platforms will have a working blur and when Android issue is sorted, so will they.

Wyrm

no, in general you only access your xbmc userdata folder, not your source path.
yesnodialog and selectdialog are already implemented. Example:

Code:

RunScript(script.toolbox,info=yesnodialog,header=Shutdown,text=$LOCALIZE[31149],yesaction=Dialog.Close(all,true)|Quit())

The blur stuff should be used in a senseful way, please don´t clutter your skins with it (depending on source image and blur radius it can take some seconds)
Not sure yet how to deal with the android situation. Will see.