<br>
<div class="gmail_quote">On Wed, Jun 25, 2008 at 9:00 PM, Raphael <<a href="mailto:rpooser@gmail.com">rpooser@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c"><br> </div></div>One thing about dumping LIRC - you can do some pretty advanced things<br>with it, and to replicate those functions using your new<br>keyboard-emulating remote it's still going to take some configuration.<br>
irexec is one example; you'd need to configure some other hotkey polling<br>program to run whatever scripts you have irexec set to run now, and the<br>hotkey would have to be a single key from the keyboard (not a<br>combination like ctl+shift+<key>). Another is having the same key on<br>
your remote do the same thing across programs like xine and mplayer.<br>With LIRC you needed to edit lircrc files, and with the keyboard-remote<br>you'll need to actually change the hotkeys in each program to do the<br>
same thing.</blockquote>
<div> </div>
<div>Very true. I've found using the multimedia keys + fluxbox keybindings to launch programs works well enough for the few scripts I need to run (one to reset the frontend mostly). But yes, you're stuck remapping keys in the various programs which not all of them support. But with the improvements to the Internal player, I no longer even use xine or mplayer anymore for any content.</div>
<div> </div>
<div>Kevin</div></div>