2014-10-28, 03:12
(2014-10-28, 02:39)gardnerd4me Wrote: Thank you for this script Milhouse, i've been getting used to it for a while now and it's great. I Use it on my Pi and it works flawless, but I have a Pi in another room with multiple profiles on it. Is there a way to direct it at a certain profile's artwork, not sure how to set that up over here.
There is a JSON method to load a profile on demand - I could add see about adding support for that and then the JSON methods would act against the currently loaded profile, although this might cause mayhem if someone is using the device at the time you run the script.
Or you can just load the profile to be updated and run the script.
Right now the script isn't particularly profile aware, for instance the X/Xd/r/R/p/P commands will default to the userdata folder of the master profile, and you would need to specify the location of each profiles userdata folder (eg. /storage/.kodi/userdata/profiles/myprofile) so that the default master profile location isn't used. You could create a [section] in your config file for each profile and configure the userdata folder within each section which would go part of the way to making the script more tolerant of profiles, then run the script specifying @section=<section-name> to work with the relevant profile. The final step would be to automatically load the profile as part of an update or query action (c/C/jd etc.), assuming the required profile isn't already loaded. The profile name would be another property to be specified in the section.