Hi Peter,
On Tue, Jan 19, 2016 at 5:46 AM, Peter Hutterer
wrote:
> A generic interface for devices that provide buttons and axes, but don't
> control the pointer. This caters for the Pad part of Wacom graphics tablets
> but could eventually also deal with remote
On Wed, Jan 20, 2016 at 08:58:09PM +0100, Benjamin Tissoires wrote:
[...]
> > @@ -138,6 +139,50 @@ enum libinput_pointer_axis_source {
> > * @ingroup device
> > * @struct libinput_tablet_tool
> > *
> > + * Available axis types for a buttonset device. It must have the @ref
> > + *
Here's the alpha for the upcoming 1.10 release.
This release adds support into Weston for a number of recently added
Wayland protocols. This includes the new drag and drop actions, new
frame and axis events, buffer co-ordinates for surface damage,
A V4L2 (Video for Linux 2) client is now
Here's the alpha for the upcoming 1.10 release. This is a big release
with a bunch of new functionality.
Drag and drop actions are now added to the Wayland API, to facilitate
negotiation of content type when dragging between a source and
destination, and provision is made to communicate the
Hello,
On 14 January 2016 at 13:51, Jonas Ã…dahl wrote:
> On Thu, Jan 14, 2016 at 11:50:29AM +0100, Michal Suchanek wrote:
>> On 14 January 2016 at 01:54, Carlos Garnacho wrote:
>> > Hi Michal,
>> >
>> > have you
>> > considered compatibility with Xdnd?
>>
On Tue, Jan 19, 2016 at 1:01 AM, Peter Hutterer
wrote:
> Synaptics, Elantech and Alps semi-mt devices all have issues with reporting
> correct MT data, even the bounding box which semi-mt devices are supposed to
> report is wrong.
>
> Synaptics devices have massive jumps
On Mon, Jan 18, 2016 at 1:57 PM, Peter Hutterer
wrote:
>
> mapping aspect ratio will be the job of the compositor. In reality, this
> will mean that one of the axes will be shortened to match the ratio.
>
Yes I believe the compositor has to do this. libinput obviously