Another option is that the client is *not* resized without supplying new input rectangles, or that a resize clears any existing rectangles. The client is then required to submit new input extents before any resize is rendered.
I think that the “just scale up the rectangles” approach isn't going to be useful; that's only useful if the client responds to a resize by drawing exactly the same thing but bigger. Clients are almost always going to respond to a resize by drawing more stuff, rather than the same stuff but bigger.
Although if we want the server to be able to resize surfaces - *and* have the user interact with them - without blocking on the client this is necessary.
Hm. I think I'm a -0 on this. Do we need to do this?
Another option is that the client is *not* resized without supplying new input rectangles, or that a resize clears any existing rectangles. The client is then required to submit new input extents before any resize is rendered.
I think that the “just scale up the rectangles” approach isn't going to be useful; that's only useful if the client responds to a resize by drawing exactly the same thing but bigger. Clients are almost always going to respond to a resize by drawing more stuff, rather than the same stuff but bigger.
Although if we want the server to be able to resize surfaces - *and* have the user interact with them - without blocking on the client this is necessary.
Hm. I think I'm a -0 on this. Do we need to do this?