Comment #7 on issue 443539 by
bugdro...@chromium.org: Create webplot to
replace mtplot
https://code.google.com/p/chromium/issues/detail?id=443539#c7
Project : chromiumos/platform/touch_firmware_test
Branch : master
Author : Charlie Mooney <
charli...@chromium.org>
Commit : 350fbc361ce8bf770a29b3a328db8c78548ae5ee
Code-Review 0 : ChromeOS Commit Bot, Shyh-In Hwang
Code-Review +2: Charlie Mooney
Commit-Queue 0 : ChromeOS Commit Bot, Shyh-In Hwang
Commit-Queue +1: Charlie Mooney
Verified 0 : ChromeOS Commit Bot, Shyh-In Hwang
Verified +1: Charlie Mooney
Commit Queue : Chumped
Change-Id : I243a8599d6b730c5a9e94dfdf3f096b2eec8ae9e
Reviewed-at :
https://chromium-review.googlesource.com/239237
Add pressure & x/y minimum parsing to RemoteTouchDevice
Webplot is using the remote touch device library as well to allow the
plotting to be done on another host instead of on the DUT. Currently
it assumes the maximum pressure value for all touch devices if 0xff.
This may be true for ChromeOS devices, but is definitely not true for
Android. (For instance one phone I tested on maxed out at 181 for
some reason)
This CL adds the max_pressure parameter to the ChromeOS and Android
remote touch device classes so that webplot can pull the real values
on whatever random device it's presented with by accessing the
device.max_pressure member.
This CL also adds parsing for the minimum values for x/y/p as currently
it assumes these are zero. I haven't actually seen any devices that
use a minimum other than that, but this addition should allow us to
write code than handles it gracefully.
Which this patch, we should be able to handle whatever weird devices
get thrown at us.
BUG=chromium:443539
TEST=manual testing on two Chromebooks and two Android phones. It was
able to determine the correct values (based on what I saw from manually
looking up the max pressure values) for all devices.
Signed-off-by: Charlie Mooney &
lt;charli...@chromium.org>
plotter.py
remote.py
test_suite.py
tests/validator/validators.py