On Sun, Jul 13, 2014 at 07:19:29PM -0400, Stephen Chandler Paul wrote:
> This event is used to signify the end of a sequence of events from the tablet.
> This is required since the wayland protocol for tablets also has a frame
> event,
> and it's impossible to tell where an event frame ends if lib
Until uinput gets that capability (likely not before 3.17) all we can do is a
racy approach of setting it after creating it. That won't work well for
anything test where libinput is already listening to udev when the device is
created, but it does work for those cases where libinput is started afte
Makes it possible to use from the touchpad code.
Signed-off-by: Peter Hutterer
---
src/filter.c| 60 ++---
src/libinput-util.h | 58 +++
2 files changed, 60 insertions(+), 58 deletions(-)
dif
A large part of palm events are situated on the far edges of the touchpad. In
a test run on a T440s while typing a long email all but 2 touch points were
located in the outer ~5% of the touchpad. Define a 5% exclusion zone on the
left and right edges in which new touchpoint is automatically assigne
On small touchpads, a touch that intends to go across the width of the
touchpad is likely to start in the edge zone. Likewise, on those touchpads the
chances of a palm event happening on the edge is small.
A minimum width of 8cm determined by an elaborate process of completely
unscientific guesswo
On small touchpads a touch that is intended to traverse much of the screen
width may start at the very edge, i.e. in the palm zone.
In that case, and if the touch moves out of the palm zone quickly enough, drop
the palm label and make it a normal touchpoint.
Signed-off-by: Peter Hutterer
---
200
This breaks when we have a device resolution set on the test devices,
specificially on the T440. The current tests use a delta of 1% of the device
which with the resulution set results in an effective delta of 3 - above the
scroll threshold.
Signed-off-by: Peter Hutterer
---
Doesn't break until 2
Any legitimate finger movement that starts in the palm area is expected to
move out of the palm area at an angle roughly orthogonal to the edge of the
touchpad. Check for the direction of the movement vector, and if it is within
the accepted cardinal/ordinal directions then proceed.
Signed-off-by:
Hi,
On Tuesday, July 15, 2014, Giulio Camuffo wrote:
> 2014-07-14 22:31 GMT+03:00 Jason Ekstrand >:
> > Guilio,
> > Would it be better to name it wl_event_queue_roundtrip and just have it
> take
> > the wl_event_queue? I guess it is sort-of a wl_display operation, but
> you
> > could argue it
Hi,
The wcap-snapshot program is now integrated into wcap-decode now but
the README didn't change, we should really fix that.
So to extract a specific frame from a wcap file (recorded using Mod+R
in weston), you can use
wcap-decode capture.wcap --frame=
Or more directly, if you just want a
On Tue, Jul 15, 2014 at 10:39 AM, Daniel Stone wrote:
> Hi,
>
>
> On Tuesday, July 15, 2014, Giulio Camuffo wrote:
>
>> 2014-07-14 22:31 GMT+03:00 Jason Ekstrand :
>> > Guilio,
>> > Would it be better to name it wl_event_queue_roundtrip and just have it
>> take
>> > the wl_event_queue? I guess
Hi,
On Tuesday, July 15, 2014, Giulio Camuffo wrote:
> 2014-07-14 22:31 GMT+03:00 Jason Ekstrand >:
> > Guilio,
> > Would it be better to name it wl_event_queue_roundtrip and just have it
> take
> > the wl_event_queue? I guess it is sort-of a wl_display operation, but
> you
> > could argue it
Dear all,
I need a snapshot program under weston/wayland. According to
wcap/README, there is a program name 'wcap-snapshot'. I can find some
screenshoter program in src/ , but I don't know how can I compile this
wcap-snapshot. Can somebody give me a hint? Thanks so much!
Best regards,
Alex
__
2014-07-15 17:32 GMT+02:00 Thiago Macieira :
> On Tuesday 15 July 2014 11:51:40 Stefanos A. wrote:
> > while (!exit) {
> > int ret = poll(&pfd, 1, -1);
> > if (ret < 0) {
> > // ret is always -1
> > exit = ret;
> > }
> > else {
> >
On Tuesday 15 July 2014 11:51:40 Stefanos A. wrote:
> while (!exit) {
> int ret = poll(&pfd, 1, -1);
> if (ret < 0) {
> // ret is always -1
> exit = ret;
> }
> else {
> // never gets here
> libinput_dispatch(input_c
On Tue, Jul 15, 2014 at 7:48 AM, Magnus Hoff
wrote:
> Hi :)
>
> I'm Magnus, and I'd like to help. I'm not scared of working with
> low-level stuff in C :) My experience is more with C++, so I will need
> some getting used to C idioms.
>
> I have successfully installed and run Wayland and Weston o
Hi :)
I'm Magnus, and I'd like to help. I'm not scared of working with
low-level stuff in C :) My experience is more with C++, so I will need
some getting used to C idioms.
I have successfully installed and run Wayland and Weston on my
machine, both on a dedicated virtual terminal and nested with
Forgot to mention that I am using libinput 0.2.0 and libsystemd 215 (latest
versions available on Arch).
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Hello everyone,
I am trying out libinput as an input backend for OpenTK[1] when running on
a VT terminal. Using weston as a reference, I have managed to get keyboard
input working as expected. The API is pleasantly terse, with very little of
the X11/XI2 non-sense remaining.
There is one thing I h
2014-07-14 22:31 GMT+03:00 Jason Ekstrand :
> Guilio,
> Would it be better to name it wl_event_queue_roundtrip and just have it take
> the wl_event_queue? I guess it is sort-of a wl_display operation, but you
> could argue it either way. Thoughts?
You have a point here, it makes more sense.
> -
20 matches
Mail list logo
