On Mon, 22 Apr 2002 13:08, Hans E. Kristiansen wrote: <snip> > The "application" in this context referes to X applications. Since the > remote control appears to the application as a keyboard and mouse ( > although the following included file lists one driver as <none>, this is > due to the current config ), the events will be interpreted by X as mouse > and keyboard events. Even if I intercept the events at the input layer ( if > this is the right nomenclature ). By 'cat /dev/input/event0' I get garble > text, but also the functionality as keyboard/mouse. You only get your remote affecting X because X is configured that way. If you change the Driver option in the InputDevice section in your XF86Config-4 (from "keyboard" to "dummy"), then no keys on the remote will do anything to X. X is incredibly configurable - you can have alternate configurations in the same file and invoke the one you want using a command line option, for example. Then, with no keyboard influence, you can do magic with lirc and /dev/input/event0 to create the X events you need.
HTH Brad _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
