2013-02-07, 18:44
Please allow me to add two of my personal frustrations
5.15 Allow filling in setting defaults using a callback function
For example the labelenum values in the settings.xml file are now hardcoded. It would be great if the possible values of the labelenum could be set during runtime using a callback function.
5.16 Service addons that start on XBMC startup should read settings from the Master User profile
When using multiple profiles and not using the login screen, the user that was logged in during the last session will login. As such, the service addon that starts at startup (start="startup" in addon.xml) will read its settings from that user profile. This means that a service addon which runs at startup must be configured the same for all user profiles or the behaviour of the service is unknown.
If such a service would always use the settings from the Master User profile the service addon would always use the correct settings.
5.16 I find especially annoying because it requires a lot of code to work arround this issue.
5.15 Allow filling in setting defaults using a callback function
For example the labelenum values in the settings.xml file are now hardcoded. It would be great if the possible values of the labelenum could be set during runtime using a callback function.
5.16 Service addons that start on XBMC startup should read settings from the Master User profile
When using multiple profiles and not using the login screen, the user that was logged in during the last session will login. As such, the service addon that starts at startup (start="startup" in addon.xml) will read its settings from that user profile. This means that a service addon which runs at startup must be configured the same for all user profiles or the behaviour of the service is unknown.
If such a service would always use the settings from the Master User profile the service addon would always use the correct settings.
5.16 I find especially annoying because it requires a lot of code to work arround this issue.