On Thu, Jan 30, 2014 at 1:42 PM, Bill Spitzak wrote:
> Ping Cheng wrote:
>
> graphics tablets:
>> * extended axis event support
>> * tool change notification (could be just button events? not sure)
>>
>>
>> Will tool id, serial number, and tool type be supported here?
>>
>
> Shouldn'
On Thu, Jan 30, 2014 at 01:42:20PM -0800, Bill Spitzak wrote:
> Ping Cheng wrote:
>
> >graphics tablets:
> >* extended axis event support
> >* tool change notification (could be just button events? not sure)
> >
> >
> >Will tool id, serial number, and tool type be supported here?
>
>
On Thu, Jan 30, 2014 at 10:30:40AM -0800, Ping Cheng wrote:
> On Tue, Jan 28, 2014 at 6:18 PM, Peter Hutterer
> wrote:
>
> > Here's a list of features I consider the minimum to get something akin to
> > feature-parity with the current X.Org-based stack. This is not a wishlist
> > for features, it
Ping Cheng wrote:
graphics tablets:
* extended axis event support
* tool change notification (could be just button events? not sure)
Will tool id, serial number, and tool type be supported here?
Shouldn't each tool be a different pointing device? It at least needs to
know which
On Tue, Jan 28, 2014 at 6:18 PM, Peter Hutterer wrote:
> Here's a list of features I consider the minimum to get something akin to
> feature-parity with the current X.Org-based stack. This is not a wishlist
> for features, it's a list of minimum requirements that covers 90% of the
> user base.
>
>
Here's a list of features I consider the minimum to get something akin to
feature-parity with the current X.Org-based stack. This is not a wishlist
for features, it's a list of minimum requirements that covers 90% of the
user base.
keyboard:
I don't think there's much to do, keyboards are fairly s
