Possible mouse mapping architecture quad-mesh -> quad-mesh transformations?

[Keith Packard]

We've explored a number of possible architectures to handle the mapping
of mouse coordinates in a transformed desktop environment. The constant
assumption in each of these architectures has been that a user
application must be involved in the transformation. My recent paper on
the topic dismissed the possibility of placing the transformation inside
the X server.

I want to revisit that assumption and try to break it. The basic problem
is that moving the mouse coordinate transformation to an external
application has proven very difficult in practice.

So, my thought is that we construct a mapping from a quadrilateral
decomposition of the physical screen coordinate space to a quadrilateral
decomposition of the root window coordinate space.

I think this can work for coordinate transformation; one question is
whether we'll need a separate data structure for hit detection; at first
glance, I think we will, but it seems like it can use another quad mesh
region structure of some kind.

Here's a sample picture of a quad-mesh -> quad-mesh transformation.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: quadmesh.svg
Type: image/svg+xml
Size: 1862 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20060628/daa2f51d/attachment.svg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20060628/daa2f51d/attachment.pgp>