Hi,
On 01/29/2016 01:48 AM, Peter Hutterer wrote:
This button sends a release N, press N+1 on each press, cycling through the
three event codes supported. This causes a stuck button since the current mode
is never released.
Long-term this better served by a set of switches that toggle
Hi,
On 01/29/2016 02:21 AM, Peter Hutterer wrote:
If a finger is resting in the software button area, it must not be counted
towards the gesture. So a two-finger movement must be a scroll event, not a
three-finger pinch.
Signed-off-by: Peter Hutterer
Patch looks
Hi,
thanks for sending this. I was actually going to start a discussion
about the existing protocol but let's go from here instead. Comments
inline:
First a question of scope: a client would only ever need to instance
one text_input object per wl_seat and then "associate" it with a
particular
If a finger is resting in the software button area, it must not be counted
towards the gesture. So a two-finger movement must be a scroll event, not a
three-finger pinch.
Signed-off-by: Peter Hutterer
---
test/gestures.c | 60
This button sends a release N, press N+1 on each press, cycling through the
three event codes supported. This causes a stuck button since the current mode
is never released.
Long-term this better served by a set of switches that toggle accordingly, for
now disable the button codes.
On Mon, Jan 25, 2016 at 05:46:56PM +0100, Hans de Goede wrote:
> Hi,
>
> On 25-01-16 04:03, Peter Hutterer wrote:
> >On Fri, Jan 22, 2016 at 11:15:55AM +0100, Hans de Goede wrote:
> >>Hi,
> >>
> >>On 22-01-16 03:06, Peter Hutterer wrote:
> >>>On Wed, Jan 20, 2016 at 11:31:42AM +0100, Hans de
2016-01-28 9:52 GMT+02:00 Jan Arne Petersen :
> There were some shortcomings in the first version of the protocol which
> makes it not really useful in real world applications. It is not really
> possible to fix them in a compatible way so introduce a new v2 of the
> protocol.
>
Hello,
Jan Arne Petersen writes:
> Fixes some shortcomings of the first version:
>
> * Use only one wp_text_input per wl_seat (client side should be
> handled by client toolkit)
> * Allow focus tracking without wl_keyboard present
These sound nice.
> * Improve update
On Thu, Jan 28, 2016 at 08:52:40AM +0100, Jan Arne Petersen wrote:
> There were some shortcomings in the first version of the protocol which
> makes it not really useful in real world applications. It is not really
> possible to fix them in a compatible way so introduce a new v2 of the
> protocol.
Hi,
On 28/01/16 10:46, Giulio Camuffo wrote:
>> +
>> +
>> + Sets the plain surrounding text around the input position. Text is
>> + UTF-8 encoded. Cursor is the byte offset within the
>> + surrounding text. Anchor is the byte offset of the
>> + selection anchor
Signed-off-by: Peter Hutterer
---
Changes to v2:
- renamed hwserial to hardware_serial
- renamed to hwid event to a hardware_id_wacom. no-one else uses this ID
type, so having a generic event with a wacom-specific type + enum is
optimistic. The next company may use a
11 matches
Mail list logo