GJones Wrote:As a suggestion, the last_run could be written to file for comparison so that when the service started (like on an xbmc restart), it could determine if there was a need to update the library on startup.
Additionally, a sleep time after startup could be specified in service.py at the beginning of the first while loop. This would allow the user to specify a period after xbmc startup to wait before updating the library. This would allow less contention between the library update, watchlist and recentlyadded scripts. On large libraries, the impact of all 3 running simultaneously is somewhat disruptive.
I think adding a startup delay is a reasonable request. For most users it is probably unneeded so the default would just be 0 but for people running a variety of startup tasks it would be nice to offset them.
I've also been toying with the idea of writing the last_run variable to a file to allow for a better means of communication between the 'program' aspect of the addon and the 'service' piece. Currently the service does not know about manually run updates; which in theory should probably reset the last_run timer back to 0 instead of running the next scheduled update.
I'll get to these soon. Thanks for the input.