2011-01-09, 03:43
Angelscry Wrote:Ok. I have finally fixed the windows command line problem, and your problem will be fixed in the next version. I will also bring back the wait state option, because finally someone need it.
thanks I appreciate it, I don't think the 360 event listener app discerns if xbmc is the current highlighted app so it just chugs along relaying input .
out of curiosity, what is the reason behind NOT entering a wait state all the time? tbh I can't think of a good reason to not always dump xbmc into a freeze state when launching a separate app thats taking display control