Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
sh...@google.com <sh...@google.com> #2
Thanks for the bug Zach,
Already looked into it to some degree and did find some lack of implementation. Upon implementing what appeared to be the right behavior some additional questions came up and I will need to follow the discussion up with some others.
Already looked into it to some degree and did find some lack of implementation. Upon implementing what appeared to be the right behavior some additional questions came up and I will need to follow the discussion up with some others.
ap...@google.com <ap...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 2f0fafb2d386a23b6f99fd61441163f2e5ba731a
Author: Shep Shapard <shepshapard@google.com>
Date: Mon Jun 01 10:06:41 2020
Creating MotionEvents with correct raw and local positions.
Previously, MotionEvents were not created with correct
raw coordinates which led to issues when Compose had
an AndroidView that in turn had Compose in it.
Fixes: 157728190
Test: ./gradlew ui:ui-core:connectedCheck --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=androidx.ui.node.PointerInteropUtilsTest
Change-Id: I1e4b7d1681ed667d6b43617429ec0a790df0b6a5
M ui/ui-android-view/integration-tests/android-view-demos/src/main/java/androidx/ui/androidview/demos/AndroidViewDemos.kt
A ui/ui-android-view/integration-tests/android-view-demos/src/main/java/androidx/ui/androidview/demos/ComplexInteractions.kt
M ui/ui-core/src/androidTest/java/androidx/ui/core/AndroidPointerInputTest.kt
M ui/ui-core/src/androidTest/java/androidx/ui/node/PointerInteropUtilsTest.kt
M ui/ui-core/src/main/java/androidx/ui/node/PointerInteropFilter.kt
M ui/ui-core/src/main/java/androidx/ui/node/PointerInteropUtils.kt
https://android-review.googlesource.com/1323233
Branch: androidx-master-dev
commit 2f0fafb2d386a23b6f99fd61441163f2e5ba731a
Author: Shep Shapard <shepshapard@google.com>
Date: Mon Jun 01 10:06:41 2020
Creating MotionEvents with correct raw and local positions.
Previously, MotionEvents were not created with correct
raw coordinates which led to issues when Compose had
an AndroidView that in turn had Compose in it.
Fixes: 157728190
Test: ./gradlew ui:ui-core:connectedCheck --info --daemon -Pandroid.testInstrumentationRunnerArguments.class=androidx.ui.node.PointerInteropUtilsTest
Change-Id: I1e4b7d1681ed667d6b43617429ec0a790df0b6a5
M ui/ui-android-view/integration-tests/android-view-demos/src/main/java/androidx/ui/androidview/demos/AndroidViewDemos.kt
A ui/ui-android-view/integration-tests/android-view-demos/src/main/java/androidx/ui/androidview/demos/ComplexInteractions.kt
M ui/ui-core/src/androidTest/java/androidx/ui/core/AndroidPointerInputTest.kt
M ui/ui-core/src/androidTest/java/androidx/ui/node/PointerInteropUtilsTest.kt
M ui/ui-core/src/main/java/androidx/ui/node/PointerInteropFilter.kt
M ui/ui-core/src/main/java/androidx/ui/node/PointerInteropUtils.kt
Description
Run this function as an app:
The button only accepts touch events on the bottom half of the button. Clicking on the top half of the button has no effect.