diff options
author | miletus@chromium.org <miletus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-09 17:55:41 +0000 |
---|---|---|
committer | miletus@chromium.org <miletus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-09 17:55:41 +0000 |
commit | 02418cca1bcf86ebd4cdec162d81c1ea10c7bed7 (patch) | |
tree | 84cb369b12b648da4fd19aee0b42a4c48cc3c7b1 /ash/DEPS | |
parent | b74340984753c1b4bfa93290952b3f3d6208b1b8 (diff) | |
download | chromium_src-02418cca1bcf86ebd4cdec162d81c1ea10c7bed7.zip chromium_src-02418cca1bcf86ebd4cdec162d81c1ea10c7bed7.tar.gz chromium_src-02418cca1bcf86ebd4cdec162d81c1ea10c7bed7.tar.bz2 |
Move touch CTM from X into Chrome
Currently we compute the touch CTM in OutputConfigurator
and push that into X. This CL makes computing the touch CTM
in DisplayController, and pushing it
into WindowTreeHostX11. This moves the functionality of
touch CTM from X into Chrome.
Basically, when there is output configuration change, we
compute the TouchCTM for each touch device, and push the
TouchCTM into the WindowTreeHostX11 that is associated
with the touchscreen. Then when X events reaching root
window, we use the CTM to map the events coordinate in
framebuffer space into the root window's coordinate space.
BUG=351019, chrome-os-partner:25788
TEST=tested on Pixel/Clapper with external touch/non-touch displays
on both extended/mirror mode. Touch events are correctly mapped to
chrome window or discarded if it is from blank region from letterboxing/pillarboxing mirror mode.
Review URL: https://codereview.chromium.org/191223007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269371 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/DEPS')
-rw-r--r-- | ash/DEPS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -21,4 +21,7 @@ specific_include_rules = { "root_window_controller\.*": [ "+ash/host" ], + "touch_transformer_controller\.*": [ + "+ash/host" + ], } |