b712d85c66
This CL is a no-op. It only changes the interface. Click events will be handled in slightly different ways depending on whether they are from pheripherals. The value of MotionEvent.getButtonState() can be used to differentiate between click events. Therefore, we add MotionEvent button state as a parameter of: * VirtualView.handleClick(), and * StripLayoutViewOnClickHandler.onClick(). As not all clicks have a button state, and the Android framework doesn't have a constant like "MotionEvent.BUTTON_NONE = 0", this CL needs to introduce this constant definition as MotionEventUtils.MOTION_EVENT_BUTTON_NONE, which will be passed to the click handlers if a click isn't detected via MotionEvents or has no MotionEvent button state. Bug: 375468032 Change-Id: I662c856d5c9fc391b15157c883affb311ae05dc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6507182 Commit-Queue: Linyu He <linyuh@google.com> Reviewed-by: Wenyu Fu <wenyufu@chromium.org> Reviewed-by: Neil Coronado <nemco@google.com> Cr-Commit-Position: refs/heads/main@{#1455914}
This directory contains UI frameworks used to build various user interface features. This directory is not intended to contain UI features (such as a keyboard).