1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
/* Alirc: Another lirc plugin for Zapping
* based on zappings template plugin
* Copyright (C) 2001 Sjoerd Simons <sjoerd@luon.net>
*
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
Why another lirc plugin for zapping?
The original lirc plugin has two big problems:
* It uses a thread to read the lirc socket and takes actions in that
thread. The X libraries aren't thread safe, so this will cause Xlib
errors.
* It reads the lirc socket itself, instead of using the lirc_client
library. The causes it to not play nice with other lirc clients. why,
an lirc client read your ~/.lircrc, in which you can specify different
modes, so you can reuse buttons among applications.. the lirc plugins assumes
the buttons are always meant for it, so bye bye reusing buttons..
How do we solve this, simply use gdk_input_add instead of an extra thread
and use the lirc_client library, like any good lirc client app would
For configuration please see the Zapping built-in documentation
(menu Help > Contents).
|
