This patch introduces a new protocol for locking and confining a
pointer. It consists of a new global object with two requests; one for
locking the surface to a position, one for confining the pointer to a
given region.
Signed-off-by: Jonas Ådahl
Reviewed-by: Peter Hutterer
Reviewed-by: Derek Fo
The wp_relative_pointer interface is an extension to the wl_pointer
interface created from wl_seat. It has the same focus, but adds the
functionality of sending relative pointer motions unhindered by
constraints such as monitor edges or other barriers. It also contains
unaccelerated pointer motion
On Wed, Dec 02, 2015 at 02:44:02PM +, Daniel Stone wrote:
> Hi,
>
> On 2 December 2015 at 03:04, Bill Spitzak wrote:
> > On Mon, Nov 30, 2015 at 3:32 PM, Peter Hutterer
> > wrote:
> >> On Mon, Nov 30, 2015 at 09:46:36PM +, Daniel Stone wrote:
> >>
> >> > > + If a seat regains the p
As of version 6, the new unstable protocol discovery semantics are
used, so lets remove the enum and request that made up the old one.
Signed-off-by: Jonas Ådahl
---
unstable/xdg-shell/xdg-shell-unstable-v6.xml | 21 -
1 file changed, 21 deletions(-)
diff --git a/unstable/xd
On Wed, Dec 02, 2015 at 06:31:48PM -0800, Jasper St. Pierre wrote:
> While we're doing this, can we remove the use_unstable_version request?
Good point. Will send a patch.
Jonas
>
> On Wed, Dec 2, 2015 at 5:06 PM, Mike Blumenkrantz wrote:
> > This copies the version 5 of the XML to a new vers
While we're doing this, can we remove the use_unstable_version request?
On Wed, Dec 2, 2015 at 5:06 PM, Mike Blumenkrantz wrote:
> This copies the version 5 of the XML to a new version 6 version, while
> at the same time the interface names are changed to use the unstable
> naming convention.
>
>
Hi Quentin,
Wayland has some Ubuntu PPA nightly builds set up, which I'm updating to
include wayland-protocols, which weston now needs to build. However,
one of the targets for these PPAs is the Ubuntu LTS 14.04, which shipped
with an older pkg-config (version 0.26) that lacks support for
PKG_NOA
On Wed, Dec 2, 2015 at 3:57 PM, Peter Hutterer
wrote:
> For the puck/lens cursor tool we need to artificially reduce proximity
> detection. These tools are usually used in a relative mode (i.e. like a
> mouse)
> and thus require lifting and resetting the tool multiple times to move
> across
> the
this change ensures that the client will set its initial state
before performing any drawing, ensuring that there is no mismatch
when creating a surface with a non-default state
(eg. maximize, fullscreen, ...)
looking at the following event flows:
1) wl_surface.attach, wl_surface.commit, xdg_shell
This copies the version 5 of the XML to a new version 6 version, while
at the same time the interface names are changed to use the unstable
naming convention.
A whitespace cleanup was done as no git-blame:ability would be lost
anyway.
Reviewed-by: Mike Blumenkrantz
Signed-off-by: Jonas Ådahl
--
On Wed, 02 Dec 2015 20:03:27 -0500
Mike Blumenkrantz wrote:
> This copies the version 5 of the XML to a new version 6 version, while
> at the same time the interface names are changed to use the unstable
> naming convention.
>
> A whitespace cleanup was done as no git-blame:ability would be lost
On Wed, Dec 02, 2015 at 10:22:56AM +0100, Hans de Goede wrote:
> Hi,
>
> On 02-12-15 02:46, Peter Hutterer wrote:
> >Keep pressure and distance mutually exclusive regardless which one of the two
> >updates.
> >
> >Signed-off-by: Peter Hutterer
> >---
> > src/evdev-tablet.c | 3 ++-
> > 1 file ch
This copies the version 5 of the XML to a new version 6 version, while
at the same time the interface names are changed to use the unstable
naming convention.
A whitespace cleanup was done as no git-blame:ability would be lost
anyway.
Reviewed-by: Mike Blumenkrantz
Signed-off-by: Jonas Ådahl
--
On Wed, Dec 02, 2015 at 04:21:56PM -0800, Jason Gerecke wrote:
> On Tue, Dec 1, 2015 at 5:46 PM, Peter Hutterer
> wrote:
> > If a tool wears out, it may have a pre-loaded pressure offset. In that case,
> > even when the tool is not physically in contact with the tablet surface it
> > will send pr
On Tue, Dec 1, 2015 at 5:46 PM, Peter Hutterer wrote:
> If a tool wears out, it may have a pre-loaded pressure offset. In that case,
> even when the tool is not physically in contact with the tablet surface it
> will send pressure events.
>
> The X.Org wacom driver has automatic pressure preload d
For the puck/lens cursor tool we need to artificially reduce proximity
detection. These tools are usually used in a relative mode (i.e. like a mouse)
and thus require lifting and resetting the tool multiple times to move across
the screen. The tablets' distance detection goes too far, requiring the
On 24/11/15 01:28 PM, Emmanuel Gil Peyrot wrote:
> Namely the single-planar YUYV, the two-planar NV12, and the
> three-planar YUV420, using the shaders already present in Weston.
>
> Signed-off-by: Emmanuel Gil Peyrot
>
> Maniphest Tasks: T13
>
> Differential Revision: https://phabricator.freed
On 24/11/15 01:28 PM, Emmanuel Gil Peyrot wrote:
> This struct serves as renderer data for linux-dmabuf buffers, and can
> contain multiple struct egl_image, simplifying this latter in the
> common non-dmabuf case.
>
> Signed-off-by: Emmanuel Gil Peyrot
> Reviewed-by: Pekka Paalanen
> Reviewed-b
On 24/11/15 01:28 PM, Emmanuel Gil Peyrot wrote:
> This allows renderers to use that struct to create their own dmabufs,
> in case they can’t import the one provided by the client directly but
> know how to convert it into a format they can render.
>
> Signed-off-by: Emmanuel Gil Peyrot
> Reviewe
If the test is filtered out and we never run it generates a false positive.
Though it isn't listed in the "Checks" summary this is a bit hard to tell when
you're running >700 tests.
Signed-off-by: Peter Hutterer
---
test/litest.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/test/
If all fingers are released in the same frame, we won't be able to find the
top-most touch.
https://bugs.freedesktop.org/show_bug.cgi?id=93204
Signed-off-by: Peter Hutterer
---
src/evdev-mt-touchpad.c | 3 ++-
test/touchpad.c | 26 ++
2 files changed, 28 inserti
Signed-off-by: Peter Hutterer
---
test/litest.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/test/litest.c b/test/litest.c
index e235bc9..ba3a308 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -1317,9 +1317,9 @@ litest_auto_assign_value(struct litest_device *d
Surface damage has a curious relationship with buffer damage. If we
change our buffer orientation, the whole buffer contents will likely
change. The application is really only supposed to tell us what parts
of the surface changed, which could still just be a subset.
Since the gl renderer uses th
We've been setting it every time a client does something that can change
the viewport (as opposed to something that does change the viewport).
However, as an example, a client could be calling set_buffer_scale() with
the same value every commit. This would lead us to performing operations
only re
When we zoom or scale an output it's possible for a single buffer
pixel to be stretched over multiple output pixels.
When this happens, if a client is sending exact damage rectangles
we can end up with incomplete updates - the client doesn't know
that the previous frame resulted in some pixel blee
On Wed, Dec 2, 2015 at 11:48 AM, Auke Booij wrote:
> I'd be happy to rebase against that, but since that hasn't been merged
> yet, I thought I'd take the current tree as a a basis.
>
> If you think having the interface:: prefix everywhere makes sense, I
> can change that if you want.
I think that
Hi,
On 2 December 2015 at 03:04, Bill Spitzak wrote:
> On Mon, Nov 30, 2015 at 3:32 PM, Peter Hutterer
> wrote:
>> On Mon, Nov 30, 2015 at 09:46:36PM +, Daniel Stone wrote:
>>
>> > > + If a seat regains the pointer capability and a client has a
>> > > pointer
>> > > + object obta
On Mon, Nov 30, 2015 at 3:32 PM, Peter Hutterer
wrote:
> On Mon, Nov 30, 2015 at 09:46:36PM +, Daniel Stone wrote:
>
> > > + If a seat regains the pointer capability and a client has a
> pointer
> > > + object obtained previously, that object may start sending
> pointer
> > > +
Looks correct to me.
I had a slightly different patch in patchwork which changes
protocol-to-docbook. It puts the enumeration into it's own statement,
rather than a nested if statement, and it adds the object:: prefix to the
documentation for all enumerations, not just the cross-object ones.
On S
On Tue, Dec 1, 2015 at 5:46 PM, Peter Hutterer
wrote:
>
> + switch (tool->type) {
> + case LIBINPUT_TABLET_TOOL_TYPE_PEN:
> + strtype = "PEN";
> + break;
> + case LIBINPUT_TABLET_TOOL_TYPE_BRUSH:
> + strtype = "BRUSH";
> +
The xwm used to automatically send to Xwayland the position of X windows
when that changed, using the x,y of the primary view of the surface.
This works fine for the desktop shell but less so for others.
This patch adds a 'send_position' vfunc to the weston_shell_client that
the shell will call whe
I'd be happy to rebase against that, but since that hasn't been merged
yet, I thought I'd take the current tree as a a basis.
If you think having the interface:: prefix everywhere makes sense, I
can change that if you want.
On 2 December 2015 at 03:09, Bill Spitzak wrote:
> Looks correct to me.
2015-11-26 10:21 GMT+02:00 Pekka Paalanen :
> On Wed, 25 Nov 2015 17:39:25 +0100
> Mariusz Ceier wrote:
>
>> Hi,
>>
>> On 25 November 2015 at 16:14, Pekka Paalanen wrote:
>>
>> > On Tue, 24 Nov 2015 18:07:34 +0100
>> > Mariusz Ceier wrote:
>> >
>> > > Hi,
>> > >
>> > > On 24 November 2015 at 17:
On Wed, 2 Dec 2015 10:51:21 +0200
Pekka Paalanen wrote:
> Hi,
>
> I don't really understand the underlying use case, but I can imagine
> adding listening sockects to wl_display by fd being useful, so I have
> no objections to this feature in general.
>
> More below.
>
>
> On Mon, 23 Nov 2015
Hi,
On 02-12-15 02:46, Peter Hutterer wrote:
Keep pressure and distance mutually exclusive regardless which one of the two
updates.
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/evdev-tablet.c b/src/evdev-table
Hi,
On 01-12-15 23:52, Peter Hutterer wrote:
These aren't real button events and they are handled elsewhere, either through
proper touch events on touchscreen or through custom handling in the touchpad
case.
Signed-off-by: Peter Hutterer
Looks good:
Reviewed-by: Hans de Goede
Regards,
Ha
Hi,
I don't really understand the underlying use case, but I can imagine
adding listening sockects to wl_display by fd being useful, so I have
no objections to this feature in general.
More below.
On Mon, 23 Nov 2015 19:59:19 -0800
Bryce Harrington wrote:
> From: Sangjin Lee
>
> Currently t
37 matches
Mail list logo
