On Tue, Aug 13, 2013 at 01:31:35PM +0200, David Herrmann wrote:
> Hi
>
> On Tue, Aug 13, 2013 at 6:50 AM, Alexander E. Patrakov
> wrote:
> > 2013/8/12 David Herrmann :
> >
> >> The implementation looks quite nice. I will not comment on the code
> >> individually, though. I'd really like to see a
2013/8/17 Peter Hutterer :
> on-screen keyboards have a one-to-one mapping. you press the button, you
> generate a key event. you don't have to worry about speed of pointer
> movement, direction of pointer movemnt, relative position of touchpoints (if
> multiple are present, etc.). the complexit
Hi
On Sat, Aug 17, 2013 at 9:49 AM, Peter Hutterer
wrote:
> On Thu, Aug 15, 2013 at 02:48:48PM -0700, Kristian Høgsberg wrote:
>> On Thu, Aug 15, 2013 at 12:10:30PM +0100, Daniel Stone wrote:
>> > Hi,
>> >
>> > On 15 August 2013 11:52, Peter Hutterer wrote:
>> > > one of the things that should b
On Thu, Aug 15, 2013 at 07:59:29PM +0600, Alexander E. Patrakov wrote:
> 2013/8/15 Peter Hutterer :
>
> > one of the things that should be done is to figure out _where_ features such
> > as this are going to be handled. In the compositor, the compositor's input
> > module, on the client side, ...
On Thu, Aug 15, 2013 at 02:48:48PM -0700, Kristian Høgsberg wrote:
> On Thu, Aug 15, 2013 at 12:10:30PM +0100, Daniel Stone wrote:
> > Hi,
> >
> > On 15 August 2013 11:52, Peter Hutterer wrote:
> > > one of the things that should be done is to figure out _where_ features
> > > such
> > > as this
On Thu, Aug 15, 2013 at 12:10:30PM +0100, Daniel Stone wrote:
> Hi,
>
> On 15 August 2013 11:52, Peter Hutterer wrote:
> > one of the things that should be done is to figure out _where_ features such
> > as this are going to be handled. In the compositor, the compositor's input
> > module, on the
On 08/15/2013 03:52 AM, Peter Hutterer wrote:
one of the things that should be done is to figure out _where_ features such
as this are going to be handled. In the compositor, the compositor's input
module, on the client side, ... ? I'm trying to figure out how to handle
this correctly, but don't
2013/8/15 Peter Hutterer :
> one of the things that should be done is to figure out _where_ features such
> as this are going to be handled. In the compositor, the compositor's input
> module, on the client side, ... ? I'm trying to figure out how to handle
> this correctly, but don't have much to
Hi,
On 15 August 2013 11:52, Peter Hutterer wrote:
> one of the things that should be done is to figure out _where_ features such
> as this are going to be handled. In the compositor, the compositor's input
> module, on the client side, ... ? I'm trying to figure out how to handle
> this correctl
On Mon, Aug 12, 2013 at 06:15:43PM +0200, David Herrmann wrote:
> Hi
>
> On Mon, Aug 5, 2013 at 12:34 PM, Alexander E. Patrakov
> wrote:
> > This patch series adds support to weston for a special type of touchpads
> > found in some laptops. These touchpads contain one physical button that
> > cov
On Tue, Aug 13, 2013 at 6:31 AM, David Herrmann wrote:
> Hi
>
> On Tue, Aug 13, 2013 at 6:50 AM, Alexander E. Patrakov
> wrote:
>> 2013/8/12 David Herrmann :
>>
>>> The implementation looks quite nice. I will not comment on the code
>>> individually, though. I'd really like to see a libtouchpad w
Hi
On Tue, Aug 13, 2013 at 6:50 AM, Alexander E. Patrakov
wrote:
> 2013/8/12 David Herrmann :
>
>> The implementation looks quite nice. I will not comment on the code
>> individually, though. I'd really like to see a libtouchpad which
>> implements all that logic. Once we start adding device driv
2013/8/12 David Herrmann :
> The implementation looks quite nice. I will not comment on the code
> individually, though. I'd really like to see a libtouchpad which
> implements all that logic. Once we start adding device drivers to
> weston, we will end up with a mess where we have to port it to e
Hi
On Mon, Aug 5, 2013 at 12:34 PM, Alexander E. Patrakov
wrote:
> This patch series adds support to weston for a special type of touchpads
> found in some laptops. These touchpads contain one physical button that
> covers the whole surface of the touchpad. Unlike the well-known Apple
> touchpad,
This patch series adds support to weston for a special type of touchpads
found in some laptops. These touchpads contain one physical button that
covers the whole surface of the touchpad. Unlike the well-known Apple
touchpad, these touchpads have markings painted on them, that designate
virtual butt
15 matches
Mail list logo
