[libinput] How I get to scroll.wheel_click_angle value using libinput?

Hello, guys. When I check mouse wheel events using libinput, I found that this wheel value was always converted by libinput. Like this: wheel_degrees.y = -1 * e->value * device- >scroll.wheel_click_angle. In function evdev_process_relative(). That value is set using udev property named

RE: [PATCH weston 0/8] IVI Screen refactoring

Hello Pekka-san, Emre-san, It is fine with me as well. This refactoring removes duplicated logic in ivi-layout and results in lower maintenance effort. Acked-by: Wataru Natsume Best Regards, Wataru Natsume --- Wataru Natsume / 夏目 亘 Advanced Driver Information

Re: [PATCH wayland-protocols v5] text: Create second version of text input protocol

This look much more promising from input method point of view comparing with previous version. I tried to implement inputmethod protocol v1 for wayland in fcitx quite some time ago, but I never put it in real use because.. it's not really practical comparing with what we have in customized im

Re: [PATCH weston 5/5] ivi-shell: forward zero size to controller

Hi, this is indeed a change in behavior, there is a case in ivi-controller where the ivi surface has not width and height it is the time between the ivi surface is created but the corresponding wayland surface did not received any buffer so far. Of cause wayland surface might also get buffer

Proposal for Anti-Keystroke Fingerprinting at the Display Server Level

== Attack Description == Keystroke fingerprinting works by measuring how long keys are pressed and the time between presses. Its very high accuracy poses a serious threat to anonymous users.[1] This tracking technology has been deployed by major advertisers (Google, Facebook), banks and

Re: [PATCH weston 0/5] simple ivi-shell fortification

Hi Pekka, I'm working in the same team with Emre and Natsume-san please find some comments below On 22.03.2016 15:48, Pekka Paalanen wrote: From: Pekka Paalanen Hi, I have written these simple patches as a side-product, and I'm proposing to merge them

Re: [PATCH wayland-protocols v5] text: Create second version of text input protocol

There is a reference implementation of this version of the protocol in QtWayland https://codereview.qt-project.org/#/c/153711/ where the text-input protocol is used to proxy the Qt input method of Qt Wayland clients to the Qt input method on compositor side. One can then use for example the

[PATCH wayland] Add API to install protocol loggers on the server wl_display

The new wl_display_add_protocol_logger allows to set a function as a logger, which will get called when a new request is received or an event is sent. This is akin to setting WAYLAND_DEBUG=1, but more powerful because it can be enabled at run time and allows to show the log e.g. in a UI view.

[RFC weston 2/2] RFC: Example of using plugin-registry

From: Pekka Paalanen The desktop shell plugin exports what is essentially the struct weston_shell_interface API. Xwayland is modified to show how it could find that API. This patch does not compile, it is merely a demonstration of the concept: the intended way to

[PATCH weston] compositor.h: Add shell_interface.get_output_work_area

From: Quentin Glidic This will allow plugins to be aware of e.g. panels, to avoid covering them with other surfaces. Signed-off-by: Quentin Glidic --- desktop-shell/shell.c | 4 +++- src/compositor.h | 1 + 2 files changed, 4

Re: [PATCH weston v6] input: use doubles in the interfaces to notify of input events

On Tue, 22 Mar 2016 17:44:54 +0200 Giulio Camuffo wrote: > This patch is a further step in the wl_fixed_t internal sanitization. > It changes the notify_* functions to take doubles instead of wl_fixed_t > but does not change how these are stored in the various input

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 05:33:57PM -0700, Andy Ritger wrote: > On Tue, Mar 22, 2016 at 09:52:21PM +, Daniel Stone wrote: > > Hi, > > > > On 22 March 2016 at 21:43, Daniel Vetter wrote: > > > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > [...] > > >> I think

Re: Introduction and updates from NVIDIA

On Tue, Mar 22, 2016 at 05:12:52PM -0700, Andy Ritger wrote: > Thanks for the thorough responses, Daniel. > > On Tue, Mar 22, 2016 at 01:49:59PM +, Daniel Stone wrote: > > Secondly, looking at the compositor-drm case, the use of the dumb > > buffer to display undefined content as a dummy