2011-02-05, 12:00
AWilco Wrote:that XBMC.ActivateWindow is a good sign.No it isn't as that's what the key is defined as before it gets redefined. Basically, the xml definition that you suggested gets ignored by xbmc hence why I tried the other definition (after googling a bit).
AWilco Wrote:Does nothing happen at all, or does it open the wrong window? again a larger log around that area would be good. Sorry I can't test this directly as I don't use a remote.The wrong window opens and is what the default for the key is without an override in the definitions file. As to debugging, you could define a key on your keyboard to run this - they should be equivalent defines once they work.
Looking at the debug, the script appears to be failing due to missing arguments (it fails on sys.argv[1]). I can't for the life of me work out how to pass arguments (which appear to be '0'. '') using the runscript command.