Looking at the new screenshots the idea of this being a suitable time to get a sleep timer into the XBMC interface came to me.
Basically if watching TV late in the bedroom I often set the TV to sleep mode for 2 different reasons. Sometimes its to stop me staying up all night watching stuff, kind on an anti-alarm clock! Othertimes its so things don't keep running all night for no reason.
Was only last night that I fell asleep while watching stuff, woke up at 5am to realise that the xbox was still on with its fan noise filling the room (seeming particularly loud at 5am, with no other sound)...then I have to get up and switch it off, or find the remote in the bed, either of which fully wakes me...at which point it's much harder to go back to sleep!
Having looked around it appears that there's already a Python script that can shutdown XBMC after a certain period of idleness, but not sure that this does what I want, in that I wanted something I can activate manually to shutdown XBMC after 'X' amount of time no matter whether the xbox is still playing music or watching video at the time.
Anyway here's my ideal specification
- New item on the 'Shutdown' half blade > 'Shutdown in X minutes'
- Clicking on that item brings up dialog with options for 15, 30, 45, 60, 120, 180, 240
(Hopefully those options would cover most lengths of content people were watching, obviously there's potential extra work to add a custom field, but would that be of interest to people?)
- Script works in background keeping an eye on the time
- When it gets to shutdown time pop-up a dialog informing user shutdown is due, with countdown timer running down from 60 seconds within dialog.
- On that dialog offer options: 'Cancel Shutdown' , 'Change Shutdown' , 'Shutdown Now'
(Change Shutdown obviously aborts counter and puts you back to original timer choice screen)
Hopefully this is all possible, not sure how multi-threaded XBMC is, and I know this is borderline of whether this is a general XBMC function, but would love it tightly integrated into the skin, hopefully PM3 could then inherit this further down the line.
To avoid flaming this is definately a 'nice to have' feature, so happy to wait until after 1.0 for things like this!