Yes, I just followed the gnome vte terminal widget code.
I will try to send v3 patch set to remove glib dependencies soon.
On Sun, 2013-07-21 at 23:22 -0500, Thomas Daede wrote:
> This is for a VT-100 style terminal emulator, right? It's designed to
> implement a grid of characters. Therefore, dra
Kai-Uwe Behrmann wrote:
> Am 19.06.2013 04:52, schrieb John Kåre Alsaker:
>> Calibration tools will require explicit privileges in order to do
>> their job. Using the full-screen color space won't be enough since
>> video card gamma correction can apply to it. I also wonder if we can
>> just remo
[Note: bcc'd linux-input, wayland-devel and xorg-devel since those are the
expected interested parties. Apologies if you get this email multiple times,
I won't do this in the future. Future announcements will only go to
input-to...@lists.freedesktop.org]
This is the first release for libevdev, a C
From: Rob Bradford
v2: Walk the array manually as wl_array_for_each is bytewise we're
storing pointers that we need to free.
---
src/input.c | 27 ---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/src/input.c b/src/input.c
index 25f2a3e..08b138c 100644
--
From: Rob Bradford
This macro allows you to correctly iterate through a list of resources
handling the opaque nature of this type.
---
src/wayland-server.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/wayland-server.h b/src/wayland-server.h
index 5109530..6dbd68d 100644
--- a/src
From: Rob Bradford
Assign each client a numerical id when the client is created for the
display. We do not want the client ids to be sparse so that they can be
used for space efficient lookups in the compositor; so when the client
is destroyed we release the id either into the next counter if it
Urgh - I misread the implementation of wl_array_for_each - I missed
that it works bytewise through the array rather than sizeof(char *)
steps.
I'll follow-up with some patches to solve this.
Rob
On 22 July 2013 17:31, Rob Bradford wrote:
> From: Rob Bradford
>
> ---
> src/input.c | 21 +++
From: Rob Bradford
This removes the use of wl_client_get_display() where the client is
derived from the focussed resource. This starts the removal of the
assumption of a single resource on a client that would be notified about
events on the focussed surface.
---
src/bindings.c| 5 +
src
From: Rob Bradford
This is the mirror function to wl_proxy_add_listener and is useful
inside client libraries to differentiate events on listeners for which
multiple proxies have been created.
---
src/wayland-client.c | 19 +++
src/wayland-client.h | 1 +
2 files changed, 20 ins
From: Rob Bradford
---
src/input.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/src/input.c b/src/input.c
index 25f2a3e..d4c28fb 100644
--- a/src/input.c
+++ b/src/input.c
@@ -366,10 +366,15 @@ weston_pointer_create(void)
WL_EXPORT void
weston_poin
From: Rob Bradford
The Wayland protocol permits a client to request the pointer, keyboard
and touch multiple times from the seat global. This is very useful in a
component like Clutter-GTK where we are combining two libraries that use
Wayland together.
This change migrates the weston input handl
From: Rob Bradford
Rather than relying on focussed resource to get the client to lookup the
drag resource with instead derive the client from the focussed surface.
This is equivalent as the focussed resource is derived from the focussed
surface in the weston_keyboard_set_focus function.
---
src
From: Rob Bradford
This is currently equivalent as there is no way for the pointer, keyboard
or touch resource to be destroyed without the client being destroyed.
This removes another place where a single resource for the focus is
assumed.
---
src/input.c | 12 ++--
1 file changed, 6 ins
From: Rob Bradford
Replace the list of resources per pointer/keyboard/touch with an array
of pointers to lists of resources from that client.
For compatability with the existing code find_resource_for_surface has
been modified to return the resource associated with the first entry in
the list an
Hi,
On 22 July 2013 11:23, Pekka Paalanen wrote:
> no, not yet, it was just a protocol RFC to get an idea. I may have
> few changes to it not posted to the list, but I won't get to them
> until next week. And the interaction with the surface/output scale
> (HiDPI) really needs to be figured out.
On Mon, 22 Jul 2013 18:11:54 +0800
Juan Zhao wrote:
> Hi pq,
>
> On Mon, 15 Jul 2013 09:14:36 -0700
> wayland-devel-requ...@lists.freedesktop.org wrote:
>
> > On Sat, 13 Jul 2013 11:34:03 +
> > "Wu, Zhiwen" wrote:
> >
> > > Hi pq,
> > > I didn't meet you at the IRC today for the time zone
Hi pq,
On Mon, 15 Jul 2013 09:14:36 -0700
wayland-devel-requ...@lists.freedesktop.org wrote:
> On Sat, 13 Jul 2013 11:34:03 +
> "Wu, Zhiwen" wrote:
>
> > Hi pq,
> > I didn't meet you at the IRC today for the time zone issue. So I
> > send this mail. Our team are using subsurface to display
From: wfu
otherwise, there will be race condition of visiting invalid surface data
---
src/compositor.c |2 ++
src/compositor.h |3 +++
src/input.c |8
3 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index e9e1166..ac2d
18 matches
Mail list logo