On 05/17/2012 08:20 AM, Jonas Ådahl wrote:
> On Thu, May 17, 2012 at 5:13 PM, Chase Douglas
> wrote:
>> On 05/17/2012 07:53 AM, Daniel Stone wrote:
>>> Hi,
>>>
>>> On 17 May 2012 15:20, Chase Douglas wrote:
>>>> I know I don't have much
On 05/17/2012 07:53 AM, Daniel Stone wrote:
> Hi,
>
> On 17 May 2012 15:20, Chase Douglas wrote:
>> I know I don't have much (any?) clout in wayland, but I feel strongly
>> enough about moving this logic to a separate library that I'm going to
>> NACK this.
On 05/17/2012 07:39 AM, Jonas Ådahl wrote:
> On Thu, May 17, 2012 at 4:20 PM, Chase Douglas
> wrote:
>> On 05/17/2012 03:18 AM, Jonas Ådahl wrote:
>>> Touchpad related code has been rewritten and moved to its own file
>>> accessed by evdev via the dispatch
On 05/17/2012 03:18 AM, Jonas Ådahl wrote:
> Touchpad related code has been rewritten and moved to its own file
> accessed by evdev via the dispatch interface.
>
> The various functionality implemented are anti-jitter (don't jumping
> around), smoother motions, touch detection, pointer acceleratio
On 05/15/2012 10:43 AM, Bill Spitzak wrote:
> It really sounds like the compositor should do this. IMHO it should
> produce *lots* of input events, so these gestures can be recognized.
> It would produce scroll events or whatever at the correct speed (or
> with a 24_8 increment on each) so th
On 05/15/2012 02:00 AM, Jonas Ådahl wrote:
> On Mon, May 14, 2012 at 7:31 PM, Chase Douglas
> wrote:
>> On 05/09/2012 02:31 PM, Jonas Ådahl wrote:
>>> Touchpad related code has been rewritten and moved to its own file
>>> accessed by evdev via the dispatch
On 05/09/2012 02:31 PM, Jonas Ådahl wrote:
> Touchpad related code has been rewritten and moved to its own file
> accessed by evdev via the dispatch interface.
>
> The various functionality implemented are anti-flicker (don't jumping
> around), smoother motions, touch detection, pointer accelerati
On 03/20/2012 05:02 PM, Kristian Hoegsberg wrote:
> On Tue, Mar 20, 2012 at 11:54:56AM +0200, Ander Conselvan de Oliveira wrote:
>> When the compositor is in a repaint cycle, input is processed only once
>> per frame. However, a call to evdev_input_device_data() would handle at
>> most 8 events at
On 02/23/2012 12:22 PM, Bill Spitzak wrote:
Chase Douglas wrote:
The client won't see the third finger if it touches outside its window.
In the wayland case, only the WM has all the info needed to determine if
a touch is part of a global gesture. The WM needs to make the decision,
no
On 02/21/2012 09:15 PM, Bill Spitzak wrote:
> Daniel Stone wrote:
>> Hi,
>>
>> On 22 February 2012 00:13, Bill Spitzak wrote:
>>> It seems like it would be better if clients got the touch events first, and
>>> the compositor only did things if the client said it was uninterested in the
>>> events.
On 02/21/2012 10:25 PM, Kristian Høgsberg wrote:
> 2012/2/21 Chase Douglas :
>> On 02/21/2012 09:16 PM, Kristian Høgsberg wrote:
>>> 2012/2/20 Chase Douglas :
>>>> On 02/17/2012 06:01 PM, Kristian Høgsberg wrote:
>>>>> - input protocol restructuring:
On 02/21/2012 09:16 PM, Kristian Høgsberg wrote:
> 2012/2/20 Chase Douglas :
>> On 02/17/2012 06:01 PM, Kristian Høgsberg wrote:
>>> - input protocol restructuring: break up events into wl_pointer
>>> (enter/leave/motion/button/axis events, set_pointer_surface reque
On 02/17/2012 06:01 PM, Kristian Høgsberg wrote:
> - input protocol restructuring: break up events into wl_pointer
> (enter/leave/motion/button/axis events, set_pointer_surface request),
> wl_keyboard (enter/leave/key events... what else... unicode event,
> set_map request? pending kb work), and w
On 12/22/2011 06:54 PM, Alex Elsayed wrote:
> Kristian Høgsberg writes:
>> Right... in the MPX sense, right? So you could have a keyboard and
>> mouse combo controlling one pointer/kb focus and the touch screen
>> being its own master device. Then maybe you could have one person
>> using the tou
On 12/22/2011 08:59 AM, Kristian Høgsberg wrote:
> 2011/12/22 Chase Douglas :
>> On 12/22/2011 07:53 AM, Kristian Høgsberg wrote:
>>> 2011/12/22 Chase Douglas :
>>>> I don't know wayland's protocol yet, but shouldn't enter/leave events
>>>
On 12/22/2011 07:53 AM, Kristian Høgsberg wrote:
> 2011/12/22 Chase Douglas :
>> I don't know wayland's protocol yet, but shouldn't enter/leave events
>> have some kind of device identifier in them? I would think that should
>> alleviate any client-side conf
On 12/22/2011 07:15 AM, Kristian Høgsberg wrote:
> On Thu, Dec 22, 2011 at 1:45 AM, Chase Douglas
> wrote:
>> On 12/21/2011 09:34 AM, Tiago Vignatti wrote:
>>> From: Tiago Vignatti
>>>
>>> Hi,
>>>
>>> Following Kristian suggestions, I
On 12/21/2011 09:34 AM, Tiago Vignatti wrote:
> From: Tiago Vignatti
>
> Hi,
>
> Following Kristian suggestions, I updated the patchset with the following:
> - driver now accumulates input coordinates to send along touch_down
> - updated the protocol touch_down event with surface field, meaning
On 07/07/2011 09:52 AM, Kristian Høgsberg wrote:
> 2011/7/7 Chase Douglas :
>> On 07/07/2011 07:28 AM, Kristian Høgsberg wrote:
>>> On Tue, Jul 5, 2011 at 1:08 PM, Chase Douglas
>>> wrote:
>>>> On
On 07/07/2011 07:28 AM, Kristian Høgsberg wrote:
> On Tue, Jul 5, 2011 at 1:08 PM, Chase Douglas
> wrote:
>> Hi Laszlo,
>>
>> On 06/29/2011 07:54 AM, Laszlo Agocs wrote:
>>>
>>> From f656362511e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
>
On 06/28/2011 07:55 AM, Kai Wohlfahrt wrote:
> I hadn't actually seen uTouch before, looks interesting. However I think
> the difference is that (for now) it seems to be an adaption to use some
> multitouch features on a standard gnome/unity/whatever desktop.
There's a distinction between uTouch a
Hi Laszlo,
On 06/29/2011 07:54 AM, Laszlo Agocs wrote:
>
> From f656362511e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
> From: Laszlo Agocs
> Date: Wed, 29 Jun 2011 17:51:29 +0300
> Subject: [PATCH] Add touch events to protocol.
>
> ---
> protocol/wayland.xml | 39 ++
On 01/24/2011 09:18 PM, Kristian Høgsberg wrote:
> I expect gesture recognition will work much the same way. The
> compositor gets the input events before anybody else and can decide
> whether it's a global gesture and keep the events to itself or to
> forward them to the application. There is no
On 01/24/2011 05:27 PM, Daniel Stone wrote:
> On Mon, Jan 24, 2011 at 01:04:35PM -0800, Bill Spitzak wrote:
>> Chase Douglas wrote:
>> I really believe passive grabs can be replaced by adding an API that
>> says "I did not handle this event". It can then be passed to
On 01/24/2011 05:31 PM, Kristian Høgsberg wrote:
> 2011/1/24 Chase Douglas :
>> I'm not advocating a free for all when it comes to input systems where
>> you pick and choose what you want. I think we should strive for an input
>> system to be extended rather than rewritt
On 01/24/2011 02:30 PM, Kristian Høgsberg wrote:
> On Sun, Jan 23, 2011 at 9:03 PM, Chase Douglas
> wrote:
>> Hi all,
>
> Hi Chase,
>
>> I haven't been involved in wayland development at all yet :), but I have
>> been working on XInput 2.1 multitouch addi
On 01/24/2011 01:57 PM, Jesse Barnes wrote:
> On Sun, 23 Jan 2011 21:03:58 -0500
> Chase Douglas wrote:
>> First I'd like to address what I think we can learn from X. X11 has a
>> core protocol and an XInput extension with two major versions. To
>> develop additions
On 01/24/2011 05:36 AM, Marty Jack wrote:
> On 01/23/2011 09:03 PM, Chase Douglas wrote:
>> Hi all,
>>
>> I haven't been involved in wayland development at all yet :), but I have
>> been working on XInput 2.1 multitouch additions and gesture work in
>> Ubun
Hi all,
I haven't been involved in wayland development at all yet :), but I have
been working on XInput 2.1 multitouch additions and gesture work in
Ubuntu. I have a few thoughts on how a new input system for wayland
might work.
To go along with that, I have no idea if these ideas have been discu
29 matches
Mail list logo
