On wl_display_add_socket(), the listening socket fd is added to the
event loop. However, wl_event_source object is not stored and hence
cannot be freed, resulting in a minor leak.
Store wl_event_source pointer in struct wl_socket so we can track it,
and destroy it on wl_display_destroy(). The
On Thu, Dec 22, 2011 at 1:45 AM, Chase Douglas
chase.doug...@canonical.com wrote:
On 12/21/2011 09:34 AM, Tiago Vignatti wrote:
From: Tiago Vignatti tiago.vigna...@intel.com
Hi,
Following Kristian suggestions, I updated the patchset with the following:
- driver now accumulates input
On Thu, Dec 22, 2011 at 9:52 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On wl_display_add_socket(), the listening socket fd is added to the
event loop. However, wl_event_source object is not stored and hence
cannot be freed, resulting in a minor leak.
Store wl_event_source pointer in
On 12/22/2011 07:53 AM, Kristian Høgsberg wrote:
2011/12/22 Chase Douglas chase.doug...@canonical.com:
I don't know wayland's protocol yet, but shouldn't enter/leave events
have some kind of device identifier in them? I would think that should
alleviate any client-side confusion.
I don't
On Thu, Dec 22, 2011 at 9:43 AM, Pekka Paalanen ppaala...@gmail.com wrote:
On Mon, 19 Dec 2011 11:56:27 +0200
Pekka Paalanen ppaala...@gmail.com wrote:
Hi Kristian,
I've been playing a lot with Valgrind the last week, and here are some
results. This patch set adds destructors to toytoolkit
On 12/22/2011 08:59 AM, Kristian Høgsberg wrote:
2011/12/22 Chase Douglas chase.doug...@canonical.com:
On 12/22/2011 07:53 AM, Kristian Høgsberg wrote:
2011/12/22 Chase Douglas chase.doug...@canonical.com:
I don't know wayland's protocol yet, but shouldn't enter/leave events
have some kind of
On Thu, 2011-12-22 at 11:40 -0800, Chase Douglas wrote:
Off the top of my head, I would think Wayland should automatically
create the equivalent of X master pointer devices for each touchscreen
device. There shouldn't be a sprite for touchscreens, though the WM
could do fancy effects like
