On Sat, Mar 23, 2013 at 2:59 PM, Andreas Pokorny <andreas.poko...@gmail.com> wrote: > Hi, > > 2013/3/23 Jerome Glisse <j.gli...@gmail.com>: >>> How would you transmit transformations that are not representable >>> by a matrix? Nothing says we are limited to matrices, that is also >>> just a special case. Or would you introduce that limitation in the >>> protocol? >> >> What kind of transformation are not representable by matrix, i am >> really curious on that. Unless you want to break the window into tile >> and show tile at different position which would be very weird. But >> still doable just have the server send an identify matrix. > > The object that displays the window buffer could be a curved surface. > Imagine HUDs with a curved glass (in that case the effect is permanent > and no client should do sub pixel rendering) > > Or consider fragment shaders applied to the window buffer. One cannot > apply fragement shader based effects without causing further glitches > when the most recent buffer relied on sub pixel layout. > > regards > Andreas
For this crazy case just don't send the matrix to the client and you done back to non sub-pixel perfect rendering. Cheers, Jerome _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel