On 12/13/2010 04:34 PM, Peter Hutterer wrote:
> On Mon, Dec 13, 2010 at 12:28:30PM -0800, Chase Douglas wrote:
>> On 12/09/2010 05:29 PM, Peter Hutterer wrote:
>>> On Mon, Dec 06, 2010 at 09:41:48AM -0800, Chase Douglas wrote:
On 12/05/2010 10:41 PM, Peter Hutterer wrote:
> if the kernel c
On Mon, Dec 13, 2010 at 12:28:30PM -0800, Chase Douglas wrote:
> On 12/09/2010 05:29 PM, Peter Hutterer wrote:
> > On Mon, Dec 06, 2010 at 09:41:48AM -0800, Chase Douglas wrote:
> >> On 12/05/2010 10:41 PM, Peter Hutterer wrote:
> >>> if the kernel can send it through one device, we can handle it,
On 12/09/2010 05:29 PM, Peter Hutterer wrote:
> On Mon, Dec 06, 2010 at 09:41:48AM -0800, Chase Douglas wrote:
>> On 12/05/2010 10:41 PM, Peter Hutterer wrote:
>>> if the kernel can send it through one device, we can handle it, right?
>>> if both are sent through the same axes (and need a serial or
On Mon, Dec 06, 2010 at 09:41:48AM -0800, Chase Douglas wrote:
> On 12/05/2010 10:41 PM, Peter Hutterer wrote:
> > if the kernel can send it through one device, we can handle it, right?
> > if both are sent through the same axes (and need a serial or something to
> > differentiate like the wacom dr
On Mon, Dec 6, 2010 at 9:41 AM, Chase Douglas
wrote:
> On 12/05/2010 10:41 PM, Peter Hutterer wrote:
>> if the kernel can send it through one device, we can handle it, right?
>> if both are sent through the same axes (and need a serial or something to
>> differentiate like the wacom drivers) then
On 12/05/2010 10:41 PM, Peter Hutterer wrote:
> if the kernel can send it through one device, we can handle it, right?
> if both are sent through the same axes (and need a serial or something to
> differentiate like the wacom drivers) then yes, they need to be split up
> into multiple devices.
I t
On Fri, Dec 03, 2010 at 05:41:59PM -0800, Ping Cheng wrote:
> On Thu, Dec 2, 2010 at 7:37 AM, Daniel Stone wrote:
> > On Thu, Dec 02, 2010 at 10:34:44AM -0500, Chase Douglas wrote:
> >> On 12/02/2010 10:28 AM, Daniel Stone wrote:
> >> > On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote
On Thu, Dec 02, 2010 at 03:37:10PM +, Daniel Stone wrote:
> Hi,
>
> On Thu, Dec 02, 2010 at 10:34:44AM -0500, Chase Douglas wrote:
> > On 12/02/2010 10:28 AM, Daniel Stone wrote:
> > > On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote:
> > >> Instead, we could create separate input
On Thu, Dec 2, 2010 at 7:37 AM, Daniel Stone wrote:
> On Thu, Dec 02, 2010 at 10:34:44AM -0500, Chase Douglas wrote:
>> On 12/02/2010 10:28 AM, Daniel Stone wrote:
>> > On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote:
>> >> Instead, we could create separate input devices for the stri
Hi,
On Thu, Dec 02, 2010 at 10:34:44AM -0500, Chase Douglas wrote:
> On 12/02/2010 10:28 AM, Daniel Stone wrote:
> > On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote:
> >> Instead, we could create separate input devices for the strip and the
> >> touchscreen. The strip would be a depe
On 12/02/2010 10:28 AM, Daniel Stone wrote:
> On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote:
>> Instead, we could create separate input devices for the strip and the
>> touchscreen. The strip would be a dependent device, and would usually be
>> attached to the same MD as the touch s
Hi,
On Thu, Dec 02, 2010 at 10:06:01AM -0500, Chase Douglas wrote:
> On 12/01/2010 05:07 PM, Peter Hutterer wrote:
> > On Fri, Nov 19, 2010 at 10:58:20AM -0500, Chase Douglas wrote:
> >> Can you provide more detail? I don't see the parallel yet.
> >>
> >> If you're thinking that each touch axis va
On 12/01/2010 05:07 PM, Peter Hutterer wrote:
> On Fri, Nov 19, 2010 at 10:58:20AM -0500, Chase Douglas wrote:
>>> on-the-side question that I just thought of: will having
>>> XIDirectTouch/XIDependentTouch on a device be equally limiting as having a
>>> single axis mode in XI 1.x?
>>
>> Can you pr
On Fri, Nov 19, 2010 at 10:58:20AM -0500, Chase Douglas wrote:
> > on-the-side question that I just thought of: will having
> > XIDirectTouch/XIDependentTouch on a device be equally limiting as having a
> > single axis mode in XI 1.x?
>
> Can you provide more detail? I don't see the parallel yet.
On 11/19/2010 01:29 AM, Peter Hutterer wrote:
> On Fri, Nov 12, 2010 at 05:35:12PM -0500, Chase Douglas wrote:
>> From: Chase Douglas
>>
>> This multitouch addition only supports slotted MT evdev protocol
>> devices. Support must be enabled at configure time using
>> --enable-multitouch. It is bui
On Fri, Nov 12, 2010 at 05:35:12PM -0500, Chase Douglas wrote:
> From: Chase Douglas
>
> This multitouch addition only supports slotted MT evdev protocol
> devices. Support must be enabled at configure time using
> --enable-multitouch. It is built on the masked valuator support in
> XInput ABI 12
From: Chase Douglas
This multitouch addition only supports slotted MT evdev protocol
devices. Support must be enabled at configure time using
--enable-multitouch. It is built on the masked valuator support in
XInput ABI 12, so do not attempt to build it for an earlier ABI.
Signed-off-by: Chase D
17 matches
Mail list logo
