Winlirc & Autohotkey Remote Problems
First of all let me say that ive used a lot of htpc software over the last few months and xbmc is the best by far. Thanks to everyone who created it.
Im having a problem with my remote, ive used the combination of winlirc and autohotkeys a number of times everyting works they way it should when xbmc isnt running for example the next button types out the character > (as far as im aware is next in xbmc) however when i run xbmc and press the button nothing happens nor does it on any of the other keys ive set up, left right up down ect.
I cant understand why this is happening, as autohotkey is emulating a keyboard when it sends these characters. (again as far as im aware)
Any help would be much appreciated, thanks in advanced.
W4rp3d
P.s if it makes any difference im using the Aeon skin (i doubt it does)
Thanks
I've tried binding XBMC keyboard hotkeys to my remote using Autohotkey with no success. XBMC doesn't seem to respond to this software.
If you're really itching to get a remote working with XBMC for Windows, it sounds like there has been some success with the MCE remote (http://www.microsoft.com/hardware/mouseandkeyboard/ProductDetails.aspx?pid=065). See the following posts.
http://xbmc.org/forum/showthread.php?t=32515
http://xbmc.org/forum/showthread.php?p=195158
I cant justify going out and buying a remote when i made the reciever out of spare parts and just used a old remote and it works 100% with in windows. I guess ill have to get up when i want to watch somthing else.
If anyone else knows any more it would be great.
I'm using Harmony 555 (setup as device HauppaugeWinTV-PVR-350 in Logitech Harmony software) with WinLIRC (Hauppauge_350.cf) and scripted AutoHotKey. Works like charm!
AutoHotKey script looks like this:
Play:
ifWinActive, XBMC
{
send {p}
}
else
{
WinActivate
}
return
When I get home tonight, I'll change my script and give it a shot. I don't know if ezechiel's approach is much different than just doing a "send {keystroke}" (which doesn't work for me). It looks like it just checks to see if XBMC is active and sends a keystroke if it is. If XBMC is minimized (not active), it restores it, so the next time you press "Play" it sends "p". So, this is questionable, but at least worth a shot.
Also, a better way to code this would be:
Play:
IfWinNotActive, XBMC
{
WinActivate
}
send {p}
return
XBMC is made active first, then the keystroke is sent.
#If you have any other info about this subject , Please add it free.# |