jhsrennie Wrote:Yes, you can create a custom keymapping file. See http://forum.xbmc.org/showpost.php?p=573912&postcount=7 for an example file.
Why is "the basic remote support" useless? I ask because we've gone to some lengths to support MCE remotes in XBMC and if there are still problems we'd like to know what they are so we can fix them!
JR
First of all i don't mean to be rude saying that.
My setup is eventghost and ordinary microsoft ir mce remote (the most popular one).
I have mapped many buttons for the following actions:
i - Keyboard i as info
DVD MENU - context menu key (very usefull sometimes)
LIVE TV - o as teh o key that displays the fps, cpu usage...
GUIDE - mapped as keyboard TAB key to switch to visualizations
RECORDED TV - Mapped as ESC key when backspace fails (exiting out of complex menus - very important).
Green microsoft button (START). - calls up XBMC
PC - emulates keypress s - for shudown (standby) also works as wake up from standby! No.1 must have key for me
Record buttom - emulates Z keystroke as per zoom function
The above changes are pretty much all i have tweaked and without them my experience with xbmc would be a disaster.
I depend on the subtitles script and navigating with the basic support is really
terrible. How are we even supposed to bring the OSD in the new versions with the mce remote anyway? Or em i the only one using it?
Also mapping a generally non working key to M as for the "new" menu key is really a bad solution as the old way works more naturally. Not to mention to re-learn to use a OSD key for apparently no reason.
On the other hand i love how native mce support feels (compared to eventgost is fantastic).