On Fri, 7 Mar 2014 14:03:48 +0200
Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> Hi all,
>
> here is the third RFC of the Wayland Presentation protocol, now
> with a complete implementation!
>
> RFCv2 can be found at
> http://lists.freedesktop.org/archives/wayland-devel/2014-January/012988
On 3 June 2014 01:25, Peter Hutterer wrote:
> On Mon, Jun 02, 2014 at 12:45:51PM +0100, José Expósito wrote:
>> Hi Peter,
>>
>> I have checked the libinput implementation and, correct me if I'm wrong, I
>> have seen that 2 fingers click is interpreted as right click, 3 fingers
>> click is interpr
I think it's unvise to have spascil logic for taskbar.
the taskbar/panel shold be treatad as a tiled window,
i sugest that instand of maximation fyling up a hole window,
it shold fill up a hole tile add put in the botum of the window order
( all other window reming on top even when the "maxemized
From: Srivardhan Hebbar
Signed-off-by: Srivardhan Hebbar
---
src/wayland-server.c |9 +
1 file changed, 9 insertions(+)
diff --git a/src/wayland-server.c b/src/wayland-server.c
index f2b1b42..7b32848 100644
--- a/src/wayland-server.c
+++ b/src/wayland-server.c
@@ -788,6 +788,15 @@
Hi,
the previous attempt at introducing a generic wl_dmabuf protocol to
Wayland didn't end too well:
http://lists.freedesktop.org/archives/wayland-devel/2013-December/012390.html
http://lists.freedesktop.org/archives/wayland-devel/2013-December/012455.html
http://lists.freedesktop.org/archives/way
From: Srivardhan Hebbar
Signed-off-by: Srivardhan Hebbar
---
src/wayland-server.c |9 +
1 file changed, 9 insertions(+)
diff --git a/src/wayland-server.c b/src/wayland-server.c
index f2b1b42..7b32848 100644
--- a/src/wayland-server.c
+++ b/src/wayland-server.c
@@ -788,6 +788,15 @@
On 3 June 2014 13:16, Peter Hutterer wrote:
> On 3/06/2014 20:25 , Shawn Rutledge wrote:
...
> the synaptics driver does support multitouch and gives you the same type of
> events as any MT device will (if you disable the in-driver gestures). It has
> done so for about 2 years now, no-one ever car
Ping?
On Mon, 24 Feb 2014 10:00:33 +0200
Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> "the callback event will arrive after the next output refresh" is wrong,
> if you interpret "output refresh" as framebuffer flip or the moment when
> the new pixels turn into light the first time. Weston
Hi,
I have a query regarding usage and functionality of a function used in seat
listener defined as seat_handle_capabilities in simple-egl.
Issue : wl_keyboard_destroy and wl_pointer_destroy are never called.
Repro steps: 1) gdb simple-egl
2) set breakpoint at simple-egl: 545
Hi,
According to [1], from which the idea of protocol dumper came, the
purpose of the protocol dumper is to track exactly how a client
communicate with the server, and to make a difference with how
WAYLAND_DEBUG=server works.
So IMHO, the protocol dumper may be implemented as a standalone program,
Hi,
We are still interested in this topic too.
One of the main comment on the latest patches was that wl_dmabuf use
DRM for buffer allocation.
This appear to be an issue since wayland doesn't want to rely on one
specific framework (DRM, or V4L2) for buffer allocation, so we have
start working on
On Thu, 16 Aug 2012 17:28:19 -0500
Rob Clark wrote:
> From: Rob Clark
>
> Signed-off-by: Rob Clark
> ---
> docs/WL_bind_wayland_display.spec |5 +
> include/EGL/eglmesaext.h |1 +
> 2 files changed, 6 insertions(+)
>
> diff --git a/docs/WL_bind_wayland_display.spec
> b/
On Mon, 9 Jun 2014 11:00:04 +0200
Benjamin Gaignard wrote:
> Hi,
>
> We are still interested in this topic too.
Hey,
cool. :-)
> One of the main comment on the latest patches was that wl_dmabuf use
> DRM for buffer allocation.
> This appear to be an issue since wayland doesn't want to rely on
Hi,
On 9 June 2014 12:06, Pekka Paalanen wrote:
> On Mon, 9 Jun 2014 11:00:04 +0200
> Benjamin Gaignard wrote:
> > One of the main comment on the latest patches was that wl_dmabuf use
> > DRM for buffer allocation.
> > This appear to be an issue since wayland doesn't want to rely on one
> > spe
Have you looked at the wl_touch protocol in the core interface at all? That
provides multiple raw touchpoints which seems to be what you're after. I
don't know if qtwaylandcompositor supports it yet, but Weston and gnome do.
On Jun 9, 2014 4:24 AM, "Shawn Rutledge" wrote:
> On 3 June 2014 13:16,
On Mon, 9 Jun 2014 12:23:18 +0100
Daniel Stone wrote:
> Hi,
>
> On 9 June 2014 12:06, Pekka Paalanen wrote:
>
> > On Mon, 9 Jun 2014 11:00:04 +0200
> > Benjamin Gaignard wrote:
> > > One of the main comment on the latest patches was that wl_dmabuf use
> > > DRM for buffer allocation.
> > > Th
Why does the kernel need to be the arbiter for buffer content constraints?
Instead, can't the client program query each hardware device for its
capabilities and then settle on a buffer format in common itself?
That said, I am writing a kernel driver for a video decoder and was looking
for ways to
A new release of libinput, 0.3, is available.
Since version 0.2, two API changes has been made:
* The fixed point type li_fixed_t (identical to wl_fixed_t) was removed
and replaced with double's.
* The enum libinput_pointer_button_state was renamed
libinput_button_state. Values was renamed a
On Mon, Jun 09, 2014 at 11:17:20AM +0530, Srivardhan wrote:
> Hi,
>
> The following are the ways in which a Protocol Dumper can be implemented:
> 1. Just before sending a message or when a message is received, the message
> can be written to a file. This change can be done in libwayland under #ifd
19 matches
Mail list logo
