[PATCH wayland] wayland-client : Fix queue_release not to call proxy_destroy

proxy_destroy could be called twice by wl_proxy_destroy and wl_event_queue_release. Then, wl_map_remove was called twice for same object id. Signed-off-by: Elvis Lee --- src/wayland-client.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/wayland-client.c b

[PATCH wayland] wayland-client : Fix duplicated proxy destroy

proxy_destroy can be called twice by wl_proxy_destroy and wl_event_queue_release. In that case, wl_map_remove should be called only once for same object id. Signed-off-by: Elvis Lee --- src/wayland-client.c |4 1 file changed, 4 insertions(+) diff --git a/src/wayland-client.c b/src

RE: Payload size and text.xml in weston

Michael. > On Thu, 2013-12-12 at 18:23 -0600, Jason Ekstrand wrote: > > Elvis, > > > > On Dec 12, 2013 2:08 AM, "Elvis Lee(KwangWoong Lee)" > > wrote: > > > While using text protocol in Weston, we encountered some cases which >

Payload size and text.xml in weston

Hello. It seems that each message has a limitation of payload size, 1024 bytes. While using text protocol in Weston, we encountered some cases which exceeds the limitation. For example, "set_surrounding_text" carries a string which is longer than 1024 bytes. I guess and hope that you guys

[PATCH] connection : correct debugging info in wl_closure_print

- print new object id on server side - print new object name when wl_registry.bind --- src/connection.c | 10 +++--- src/wayland-client.c |4 ++-- src/wayland-private.h |2 +- src/wayland-server.c |6 +++--- 4 files changed, 13 insertions(+), 9 deletions(-) diff --git a/s