• Yash Malik's avatar
    VR: Clean-up input handling · 4e8bbd10
    Yash Malik authored
    Before this CL, target_element in UiInputManager would also be the input
    caputring element. In this CL, the target_element is always the element behind
    the ray. This makes the code easier to read and simplifies hover events.
    
    The only functional change in this CL is that we send hover events to non-input
    caputring elements. For example, if we have element 1 and element 2, clicking on
    element 1 and moving to element 2 will send HoverLeave to element 1 and
    HoverEnter to element 2.
    
    This CL also removed the unused ButtonState::CLICKED
    
    Bug: 
    Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
    Change-Id: I1be4a8f3cf593e6341df0540efcfd0bc5456f217
    Reviewed-on: https://chromium-review.googlesource.com/830886Reviewed-by: default avatarIan Vollick <vollick@chromium.org>
    Commit-Queue: Yash Malik <ymalik@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#524489}
    4e8bbd10
ui_input_manager.cc 15.6 KB