On Thu, May 10, 2012 at 10:59:17PM +0100, Daniel Stone wrote:
> Hi,
>
> On 10 May 2012 22:11, Kristian Høgsberg wrote:
> > I agree that we need to get evdev a little more under control, but I
> > was thinking that we'd be able to decide up front that a device is a
> > touchpad, a mouse a keyboard
Hi,
On 10 May 2012 22:11, Kristian Høgsberg wrote:
> I agree that we need to get evdev a little more under control, but I
> was thinking that we'd be able to decide up front that a device is a
> touchpad, a mouse a keyboard or such. In evdev_configure_device()
> we'd decide what it is and just s
On Thu, May 10, 2012 at 11:11 PM, Kristian Høgsberg wrote:
> On Wed, May 09, 2012 at 11:31:43PM +0200, Jonas Ådahl wrote:
>> By adding an 'evdev_dispatch' struct to the dispatch_list in
>> 'evdev_input_device' the 'process' function in the associated interface
>> will be called with received input
On Wed, May 09, 2012 at 11:31:43PM +0200, Jonas Ådahl wrote:
> By adding an 'evdev_dispatch' struct to the dispatch_list in
> 'evdev_input_device' the 'process' function in the associated interface
> will be called with received input events. The process function can
> either handle the event and r
By adding an 'evdev_dispatch' struct to the dispatch_list in
'evdev_input_device' the 'process' function in the associated interface
will be called with received input events. The process function can
either handle the event and return a non-zero integer or return zero and
the generic fallback hand
