configure.html

很少见的linux下的红外口的工具

	  <em>x</em>=<em>repeat</em>*<em>multiplier</em>, where repeat
	  is the number of repeated signals. <em>max</em> specifies
	  the maximum number of pixels the pointer can move due to a
	  single command.
	</P>
      </DD>
      <DT>ACTIVATE&nbsp;&nbsp;&lt;<em>remote</em>&gt; &lt;<em>button</em>&gt;</DT>
      <DT>TOGGLE_ACTIVATE&nbsp;&nbsp;&lt;<em>remote</em>&gt; &lt;<em>button</em>&gt;</DT>
      <DD>
	<P>
	  I recommend that you use a special button to activate the
	  mouse daemon with this command. You will see whenever the
	  daemon is activated/deactivated directly on the screen. If
	  you omit this command the daemon will always be active.
	</P>
	<P>
	  The difference between ACTIVATE and TOGGLE_ACTIVATE is how
	  you leave the mouse mode. With TOGGLE_ACTIVATE you have to
	  press the button that you use to enter the mode to leave
	  it. With ACTIVATE you will leave mouse mode as soon as you
	  press a button that is not used for any function in the
	  config file.
	</P>
      </DD>
      <DT>MOVE_ [ N [ E | W ] | E | S [ E | W ] | W ]&nbsp;&nbsp;&lt;<em>remote</em>&gt; &lt;<em>button</em>&gt;</DT>
      <DD>
	<P>
	  The obvious functionality. You can even get better
	  granularity by combing different commands (copied from the
	  config file for AnimaX remotes):
	</P>
	<PRE>
MOVE_N    ANIMAX_MOUSE_PAD   MOUSE_NNE
MOVE_NE   ANIMAX_MOUSE_PAD   MOUSE_NNE</PRE>
	<P>
	  This also demonstrates that all commands are executed
	  beginning at the top.
	</P>
      </DD>
      <DT>MOVE_[IN|OUT]&nbsp;&nbsp;&lt;<em>remote</em>&gt; &lt;<em>button</em>&gt;</DT> 
      <DD>
	<P>
	  This will only work with IntelliMouse and IMPS/2 protocols
	  and indicates movement of the wheel.
	</P>
      </DD>
    </DL>
    
    <P>
      '*' is allowed as wild card for button and remote. Please note
      that every line that fits to the received signal will be
      executed. Parsing starts at the top of the file.
    </P>
    
    <!-- .lircrc file format ++++++++++++++++++++++++++++++++++++++++++++++ -->
    
    <A NAME="lircrc_format"></A><HR>
    <H1 ALIGN="CENTER">The .lircrc file format</H1>
    <HR WIDTH="70%">
    
    <P>
      At this point all you need are the tools, which react on the
      signals decoded by lircd. To do this you need a file called
      <em>.lircrc</em>. It should be placed in your home
      directory. The idea is to have configuration information of all
      clients in one place. That lets you keep a better overview of
      clients and simplifies the use of modes explained later.
    </P>
    <P>
      First I will explain the syntax of the .lircrc file itself.  The
      config file for LIRC tools consists of one or more of the
      following constructions:
    </P>
    <PRE>
    begin
	prog	= ...
	remote	= ...
	button	= ...
	repeat	= ...
	config	= ...
	mode	= ...
	flags	= ...
    end</PRE>
    <P>
      Bringing it to the point the above says which program
      (<em>prog</em>) should do what (<em>config</em>, <em>mode</em>,
      <em>flags</em>) if you press a certain button (<em>remote</em>,
      <em>button</em>) a specified time (<em>repeat</em>).
    </P>
    <DL>
      <DT>prog</DT>
      <DD>gives the name of the program that should receive the
	configstring given in config.
      </DD>
      <DT>remote, button</DT>
      <DD>specify a key of a remote control that launches an
	action. Key sequences can be specified by giving more then one
	remote/button string. The character '*' can be used as a wild
	card for remote or button. The default for remote is '*'. The
	remote name must always be given before its according
	button. When using key sequences a given remote is valid for
	all following buttons until you specify another remote.
      </DD>
      <DT>repeat</DT>
      <DD>tells the program what shall happen if a key is repeated.  A
	value of zero tells the program to ignore repeated keys.  Any
	other positive value 'n' tells the program to pass the config
	string every 'n'-th time to the according application, when a
	key is repeated. The default for repeat is zero.
      </DD>
      <DT>config</DT>
      <DD>is the string that will be passed to the according
	application whenever the specified key sequence is received by
	lircd. If you give more than one config string, the config
	strings will be passed to the applications by turns. With this
	feature you can for example implement toggle buttons.<BR>
	
	You can pass non-printable characters to applications with all
	standard C escape sequences (most common are: \n = line-feed,
	\r = carriage return, \t = tab, \e = escape,
	\&lt;<em>n</em>&gt; = ASCII code in octal representation,
	\x&lt;<em>n</em>&gt; = ASCII code in hexadecimal
	representation, \\ = backslash). Additionally you can supply
	Ctrl-X by specifying \X where X is an upper character or
	@. For example \C is Ctrl-C.
      </DD>
      <DT>mode</DT>
      <DD>tells the program to enter a special mode. You can group
	several configurations by putting them into the following,
	where mode stands for the mode where these configurations
	should be active: 
	
	<PRE>
    begin mode
	...
    end mode</PRE>
	
	If mode is equal to the name of a client application this
	application will always start in this mode. Consider this
	situation: you want to start <em>xawtv</em> with
	<em>irexec</em> and enter the <em>tv</em> mode. Then irexec
	would enter the tv mode but xawtv would begin without any mode
	enabled. By renaming the mode from <em>tv</em> to
	<em>xawtv</em> you can solve this problem.

	<br>Another way to specify a startup mode is by using the
	startup_mode flag as described below.<BR>
	<BR>
	<em>Caveat:</em> In order to avoid many identical entries all
	actions that modify the mode a program currently is in are
	independent of the <em>prog</em> token.
      </DD>
    </DL>
    The following are valid flags:
    <DL>
      <DT>once</DT>
      
      <DD>
	This is only allowed in conjunction with the mode
	directive. The config string is passed to the application only
	the first time the mode is entered or you have explicitly left
	this mode. This is useful for starting an application whenever
	you enter a special mode.
      </DD>
      <DT>quit</DT>
      <DD>Usually all configurations are examined if they have
	to be executed. You can stop this immediately with this flag.
      </DD>
      <DT>mode</DT>
      <DD>This is only allowed within a mode block. It tells the
	program to leave this mode.
      </DD>
      <DT>startup_mode</DT>
      <DD>
	Tells the program to start in the mode given in the mode
	keyword.  The following example tells the program to start in
	the <em>browser</em> mode
	<PRE>
begin
	flags = startup_mode
	mode = browser
end</PRE>
      </DD>
    </DL>
    
    <P>
      Ok, now a simple example for a <em>.lircrc</em> file (supposed
      you use an AnimaX remote and use the sample files for this
      remote from the remotes/ directory. If you have another remote
      change <em>remote=</em> and <em>button=</em> according to your
      remote [this definitions are made in the <em>lircd.conf</em>
      file] )
    </P>
    
    <PRE>
    begin
        remote = ANIMAX
        button = MENU_DOWN
        prog   = irexec
        repeat = 0
        config = echo "Hello world!"
    end</PRE>
    <P>
      If you have saved this as <em>.lircrc</em> in your home
      directory, start <em>irexec</em>. Press the button which is
      selected in the <em>button=</em> line and you will see a 'Hello
      world!' on your screen. As you can see irexec is a simple
      program launcher. Of course you can do a lot more than just
      start programs.
    </P>
    
    <P>
      If you start a LIRC client program, it reads your ~/.lircrc and
      reacts only on prog= entries which point to itself. All programs
      should give you the possibility to use an alternative config
      file. If you have included more than one program in your
      .lircrc, then start all these programs, they react only to their
      according entries in .lircrc. This also leads to a disadvantage
      of the mode concept. If you don't start all client programs at a
      time the mode they have to maintain may differ between
      applications. Also key sequences might not be recognized equally
      because all programs then don't have the same starting point.
    </P>
    

<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->

		<BR><BR>
		<CENTER>[<A HREF="http://www.lirc.org/">LIRC homepage</A>]<BR>
		  <I>The LIRC Manual, last update: 12-Sep-2002</I></CENTER>
		<BR><BR>
	      </TD>
	      <TD WIDTH="15%">&#160;<BR></TD>
	    </TR>
	  </TABLE>
	</TD>
      </TR>
      <TR>
	<TD CLASS="menu" WIDTH="100%">&#160;<BR>
	</TD>
      </TR>
    </TABLE>
  </BODY>
</HTML>