Summary: | the xinput Coordinate Transformation Matrix is undocumented and does nothing visible | ||
---|---|---|---|
Product: | xorg | Reporter: | Michal Suchanek <hramrach> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | dapicester, peter.hutterer |
Version: | 7.6 (2010.12) | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 27688 |
Description
Michal Suchanek
2011-06-20 02:42:37 UTC
I tried also using inverting the axes with the following matrices: a. [-1 0 0 0 1 0 0 0 1] for X axis b. [ 1 0 0 0 -1 0 0 0 1] for Y axis c. [-1 0 0 0 -1 0 0 0 1] for both axes without any effect. $ Xorg -version X.Org X Server 1.9.5 Release Date: 2011-03-17 X Protocol Version 11, Revision 0 $ xinput --version xinput version 1.5.3 XI version on server: 2.0 The property currently only works for absolute devices though we're trying to fix this but possibly not until 1.11 or 1.12. It is documented here: http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage Is progress on supporting the transformation matrix for relative devices being tracked anywhere (roadmap, bugzilla, something)? (In reply to comment #2) > The property currently only works for absolute devices though we're trying to > fix this but possibly not until 1.11 or 1.12. It is documented here: > > http://wiki.x.org/wiki/XInputCoordinateTransformationMatrixUsage as of 1.14, the coordinate matrix can now be used for relative devices too -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/412. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.