Doesn't need XCB API changes per se, I think, just to the image library. <div class="gmail_quote"><div dir="ltr">On Wed, Jan 30, 2019, 13:39 Keith Packard <<a href="mailto:keithp@keithp.com">keithp@keithp.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">paul ewing <<a href="mailto:pcewing@outlook.com" target="_blank">pcewing@outlook.com</a>> writes: > It's not just the xcb_image_put request that needs to be split up. Separate > images have to be created via multiple calls to xcb_image_create and a call to > xcb_image_put has to be made for each image. Yeah, some API changes to make it easy to put sub-images would be useful. > I suppose that xcb_image_put could detect if the image is too large and split > the image up internally but then you have the problem Bart mentioned where > there are multiple cookies to track each request and it's unclear what to > return. With xcb API changes to allow sub-image puts, creating a util function to put the whole image and split it up would be pretty easy. -- -keith </blockquote></div>