Wacom Cintiqs and some DTK/DTU devices have a sensor larger than the
underlying display. Clamp any data outside the screen area to the screen area.
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 27 +
src/evdev.c| 1
On Mon, Feb 15, 2016 at 02:19:43PM +, Ucan, Emre (ADITG/SW1) wrote:
> We have to block other threads from reading events. Otherwise other threads
> may assign done event to the default queue, if they call
> wl_display_read_events before setting the queue for the callback proxy.
> This would cau
It doesn’t make sense to fail the entire build when jpeglib isn’t
present, so this commit makes it optional just like libwebp in the
previous one, disabled with --without-jpeg and forced with --with-jpeg.
Signed-off-by: Emmanuel Gil Peyrot
---
Changes since v1:
- Added a --without-jpeg and a --wi
The current way was enabling WebP support whenever libwebp was found,
giving no way to the user to disable it if they had the library
installed but didn’t want to link against it. This adds a
--without-webp configure option to never link against it, and a
--with-webp one to fail the build if it is
We have to block other threads from reading events. Otherwise other threads
may assign done event to the default queue, if they call
wl_display_read_events before setting the queue for the callback proxy.
This would cause a deadlock in wl_display_dispatch_queue,
because the default queue is not dis
From: PrasannaKumar Muralidharan
I am implementing dial input device support and would like to get feedback on
the code that I have implemented so far. Did not implement test cases as of
now, any pointers on how the test framework works will be helpful.
Smartwatch can use dial input, Car can u
On Thu, Feb 11, 2016 at 01:52:36PM +0100, Carlos Garnacho wrote:
> The xdg_launcher interface is added for the launcher, it's used
> to notify of the startup ID to be transmitted to the launchee,
> plus notifications about the startup success/failure.
>
> On the launchee side, we now have xdg_shel
On Mon, 15 Feb 2016 16:44:54 +0900
nic...@nicesj.com wrote:
> Dear all,
>
> I'm sorry to taint this mailing list.
> I cannot access the patchwork now, server tells me that I have no
> permissions..
>
> how can I access it? is therr any changes that I should know?
Hi,
I expect this is fallout