Chase Douglas writes:
> I don't think anyone is forgetting about indirect devices, at least I'm
> not :). However, their use scenarios are a bit easier to deal with
> because there's no pointer emulation.
>
> We will also want the ability to have a touchscreen "attached" to a real
> keyboard. Ima
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
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 touch screen UI, and another person using the kb/mous
On Wed, Dec 21, 2011 at 12:34 PM, 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,
On Thu, 2011-12-22 at 11:40 -0800, Chase Douglas wrote:
> >> Off the top of my head, I would think Wayland should automatically
> >> create the equivalent of X master pointer devices for each touchscreen
> >> device. There shouldn't be a sprite for touchscreens, though the WM
> >> could do fancy ef
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
have some kind of device identifier in them? I would think
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
>>> have some kind of device identifier in them? I would think that should
>>> alleviate any client-side confusion.
>
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 confusion.
>
> I don't think so. To be clea
2011/12/22 Chase Douglas :
> 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 updated the patchset with
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 updated the patchset with the following:
>>> - driver now accu
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 updated the patchset with the following:
>> - driver now accumulates input coordinates to send along touch_down
>> - upda
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
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 the focus
surface of a touch device
- compositor now uses
13 matches
Mail list logo
