Pekka Paalanen wrote:
Sounds right. My main concern was that the scale width+height completely
replaces all uses of the buffer width+height in the visible compositor
api (the buffer width+height is needed to figure out where the memory
for the crop region is, but should be ignored otherwise).
This thread is about protocol. It says nothing about Weston's
internal implementation details.
My question *is* about the protocol.
Let me try again: to a client, after it sends a scale of a 100x100
buffer to 200x200, is there any indication of that original 100x100 size
in any protocol events or requests afterwards, or does it work precisely
the same as though they sent an unscaled 200x200 buffer?
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
