<html><body>
<p>Thanks!<br>
But, are there any other ways can solve this problem then?<br>
it seems not so easy to solve this problem! another application would separated from MythTV now.<br>
<br>
Thanks!<br>
<br>
Jerry <br>
<tt><br>
<br>
On 10/08/2007 04:01 AM, Xi Jiarong wrote:<br>
>> I have a problem about MythTV and remote control:<br>
>> My Mythtv and remote control work properlly together now.<br>
>> However when I open other application or windows when Mythtv is running,and<br>
>> then didn't let the mythtv ui as be the frontend focused UI, but I found<br>
>> Mythtv UI would still be controlled by remote control even it is not on the<br>
>> front as been focused.<br>
>> <br>
<br>
>Yep. LIRC has no concept of Window focus because LIRC is often used for<br>
>things that have no windows to focus (i.e. my Internet radio script). <br>
>Instead LIRC /always/ sends command strings as specified in the LIRC<br>
>configuration file (typically ~/.lircrc) to /all/ clients. It is<br>
>completely up to the client to determine whether or not the action<br>
>should be performed at the time.<br>
<br>
>When MythTV starts another application, it stops listening to LIRC<br>
>commands until the other application exits. If you start an application<br>
>on your own, Myth has no way of knowing it should ignore the LIRC commands.<br>
<br>
<br>
>> How to solve this problem so that let Remote control not to control Mythtv<br>
>> UI when I use remote cotrol for other application which is the current<br>
>> frontend focused window?<br>
<br>
>Start the other application through MythTV (look at the EXECTV examples<br>
>in /usr/{,local/}share/mythtv/tvmenu.xml and note that there is an EXEC<br>
>equivalent for when you start an application that doesn't need a capture<br>
>card).<br>
<br>
>The only other option is to use LIRC modes (<br>
</tt><tt>><a href="http://lirc.org/html/configure.html#lircrc_format">http://lirc.org/html/configure.html#lircrc_format</a></tt><tt> ), but this approach<br>
>requires a lot of setup (possibly with redundant configuration<br>
>information--depending on how you want your modes to work), requires<br>
>synchronizing the "current" mode for all applications (<br>
</tt><tt>><a href="http://lirc.org/html/lircrcd.html">http://lirc.org/html/lircrcd.html</a></tt><tt> ), as well as UI issues (having to<br>
>devote buttons specifically to entering and exiting modes and/or having<br>
>to remember which mode you're in). In other words, you probably don't<br>
>want to do it (I know I don't, and I actually did it once just to verify).<br>
<br>
Mike</tt><br>
<br>
<br>
<br>
<br>
<br>
Best Regards!<br>
<br>
----------------<br>
Jerry<br>
</body></html>