Introduce wl_resource_queue_event() for sending events later

Some events, such as the display.delete_id, aren't very urgent and we
would like to not always send them immdiately and cause an unnecessary
context switch.  The wl_resource_queue_event() function will place the
event in the connection output buffer but not request the main loop to
poll for writable.  The effect is that the event will just sit in the
output buffer until a more important event comes around and requires
flushing.

1 files changed, 0 insertions, 4 deletions

diff --git a/src/wayland-client.c b/src/wayland-client.c
index 8f3e106..5845698 100644
--- a/src/wayland-client.c
+++ b/src/wayland-client.c
@@ -469,10 +469,6 @@ wl_display_iterate(struct wl_display *display, uint32_t mask)
 
 	len = wl_connection_data(display->connection, mask);
 
-	if (wl_debug && (mask & WL_DISPLAY_READABLE))
-		fprintf(stderr,
-			"[-----------] wakeup, read %d bytes\n", len);
-
 	while (len > 0) {
 		if (len < sizeof p)
 			break;