XBMC sees EventGhost as neither a keyboard or remote. It's sending XBMC the raw actions. So, if you look at Keymap.xml in the remote section:
Code:
<left>StepBack</left>
EventGhost is sending the actual "StepBack" action rather than a "left" button press. Both methods are doable, but the way it is implemented now allows for much more control over what you can do. The downside is it does not work well for contextual actions like up, down, etc.
If we can determine a subset of commands to be sent as actual button presses that Keymap.xml will respect I am willing to add it. I just don't want to dump every key in as an action along side the actual actions because the combined list would be over 100 items long and most of the button presses would never be used.
Quote:
Also, has anyone else noticed XBMC will go "idle" with input coming from an EventClient. Set your idle time really low and the screensaver to dim and just browse around the menus until the idle time is up.
The event server in XBMC is a work in progress. If you come across anything like that create a ticket. The owner of the event server code (d4rk) is pretty quick to get on issues.