2010-01-28, 02:35
This actually is related to HTE, because a lot of us are spending a lot of time troubleshooting.
When troubleshooting XBMC, the XBMC team recommends that you close out XBMC and relaunch XBMC after each troubleshooting step so as to keep the debug log short and easy to read.
This procedure allows you to do that much quickly and easily than using your mouse to close out XBMC - and really helps to get rid of the keyboard once everything's working smoothly.
Code is below - and full write-up with script and fully compiled versions are here. Hope it helps someone!
When troubleshooting XBMC, the XBMC team recommends that you close out XBMC and relaunch XBMC after each troubleshooting step so as to keep the debug log short and easy to read.
This procedure allows you to do that much quickly and easily than using your mouse to close out XBMC - and really helps to get rid of the keyboard once everything's working smoothly.
Code is below - and full write-up with script and fully compiled versions are here. Hope it helps someone!