<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 17, 2012, at 5:01 PM, John Kåre Alsaker wrote:</div></div><div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"><br></font></blockquote><blockquote type="cite">Then a client such as gimp could draw all it's display into a single buffer.<br></blockquote><blockquote type="cite">To get the different color correction of the center display, it would<br></blockquote><blockquote type="cite">declare a subsurface containing this and set it's color correction<br></blockquote><blockquote type="cite">differently using the wayland api. This would only allocate one buffer,<br></blockquote><blockquote type="cite">which would save memory, but more importantly it should make internal code<br></blockquote><blockquote type="cite">in gimp easier as you could work around a toolkit that assumes only one<br></blockquote><blockquote type="cite">output buffer.<br></blockquote>My approach to color correct rendering in Wayland is to let the<br>compositor handle it and have the clients simply specify which color<br>space they are using. Only the compositor can render clients correctly<br>when they are displayed on multiple monitors (unless we introduce a<br>way to set a buffer per-output).<br></div></blockquote><div><br></div>Yes this is what I am assuming.</div><div><br></div><div>What I am asking is if it makes sense for a client to draw two different color spaces into the same buffer. The larger area is color space A, and a rectangular subarea is color space B. It then tells wayland to make the main window color space A, and then makes a subwindow with the clipped subarea and tells wayland that it is color space B.</div><div><br></div><div>The reason is to save buffer space, and also to work around toolkits and drawing api's where it is a lot more practical to draw everything into the same buffer.</div><div><br></div><br></body></html>