Posts: 2,274
Joined: Feb 2009
Reputation:
30
opdenkamp
Retired Team-Kodi Member
Posts: 2,274
unless I haven't seen it yet, I don't think we added any code for that on the add-on interface. so the answer would be "no". why would you want that anyway?
opdenkamp / dushmaniac
xbmc-pvr [Eden-PVR builds] [now included in mainline XBMC, so no more source link here :)]
personal website: [link]
Found a problem with PVR? Report it on Trac, under "PVR - core components". Please attach the full debug log.
If you like my work, please consider donating to me and/or Team XBMC.
Posts: 21
Joined: Jun 2010
Reputation:
0
danips
Junior Member
Posts: 21
They may be useful when you can obtain very big amounts of EPG info:
- epg.daystodisplay: if you know how many days are going to be displayed you can get only the useful time frame.
- epg.update: when consulting highly mutable info or with no certainties to be stable, you may consult only before the update is going to happen, instead of setting random periodic checks.
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
these should definitely be exported in the add-on interface, not through reading guisettings.
Posts: 2,274
Joined: Feb 2009
Reputation:
30
opdenkamp
Retired Team-Kodi Member
Posts: 2,274
makes sense.
I could easily add a method on the interface that XBMC can use to notify an add-on that some settings value relevant to that add-on changed.
something like "OnSettingChanged(const char *strSettingName, const void *newValue)"
opdenkamp / dushmaniac
xbmc-pvr [Eden-PVR builds] [now included in mainline XBMC, so no more source link here :)]
personal website: [link]
Found a problem with PVR? Report it on Trac, under "PVR - core components". Please attach the full debug log.
If you like my work, please consider donating to me and/or Team XBMC.