2010-02-02, 02:55
Hi,
I have a custom keymap.xml file where I configure a specific button on my remote to close XBMC and I do use that button a lot as my HTPC is not used only for XBMC. That button calls the XBMC.Quit() function (or XBMC.Exit()? I don't quite remember what you guys call it, but it's one of those I believe).
What happens is that sometimes (more often than I would like) XBMC doesn't close at all, but the process seems to freeze. The image on screen doesn't change, pressing other remote buttons doesn't do anything, it just freezes. If I happen to press many times the buttons on the remote, it will eventually stall (at some extent) my computer as the led screen on the PC case I have scrolls the time and that just freezes too after too many remote presses.
However, in both situations, just a XBMC freeze or if the led screen also freezes, I normally can just press Ctrl+Shift+Esc to bring the task manager and kill the XBMC process.
But this is annoying...
I'm using SVN but not a very recent version, just a couple of revisions after Babylon. This was not happening previously to Babylon where I was also using SVN versions but hadn't updated in while until Babylon came along.
Any reason for this behavior? How can I properly close XBMC using my remote without this problem?
I have a custom keymap.xml file where I configure a specific button on my remote to close XBMC and I do use that button a lot as my HTPC is not used only for XBMC. That button calls the XBMC.Quit() function (or XBMC.Exit()? I don't quite remember what you guys call it, but it's one of those I believe).
What happens is that sometimes (more often than I would like) XBMC doesn't close at all, but the process seems to freeze. The image on screen doesn't change, pressing other remote buttons doesn't do anything, it just freezes. If I happen to press many times the buttons on the remote, it will eventually stall (at some extent) my computer as the led screen on the PC case I have scrolls the time and that just freezes too after too many remote presses.
However, in both situations, just a XBMC freeze or if the led screen also freezes, I normally can just press Ctrl+Shift+Esc to bring the task manager and kill the XBMC process.
But this is annoying...
I'm using SVN but not a very recent version, just a couple of revisions after Babylon. This was not happening previously to Babylon where I was also using SVN versions but hadn't updated in while until Babylon came along.
Any reason for this behavior? How can I properly close XBMC using my remote without this problem?