Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Hi - thanks for raising this, I'll dig into our SwipeDismissableNavHost and try to find out why we didn't support the back button already. Will report back on this thread.
jb...@google.com
An early draft of SwipeDismissableNavHost did implement back button support, but it was thought not to be required - we will submit a change to add the support back again.
ma...@gmail.com
Branch: androidx-main
commit 78d498661680a95d2705d5e6dbb1c0438c50fa30
Author: stevebower <stevebower@google.com>
Date: Tue Dec 14 13:42:48 2021
Support back button in SwipeDismissableNavHost.
Added back button handling for navigation to
SwipeDismissableNavHost, using the implementation
from Compose Material NavHost. This enables use
of the emulator's back button for local testing,
as well as in any devices that support a hardware back button.
Test: Run tests for wear.compose.navigation.
Bug: 210205624
Relnote: "We have added a back button handler to
SwipeDismissableNavHost, so that pressing
back navigates to the previous level
in the navigation hierarchy."
Change-Id: I5b08689b1651c1aae5f038f058956007df398909
M wear/compose/compose-navigation/build.gradle
M wear/compose/compose-navigation/src/androidTest/kotlin/androidx/wear/compose/navigation/SwipeDismissableNavHostTest.kt
M wear/compose/compose-navigation/src/main/java/androidx/wear/compose/navigation/SwipeDismissableNavHost.kt
ap...@google.com
Branch: androidx-master-dev
commit 13352b5a3b2aca96bba64662027347d66d39c6b5
Author: Ian Lake <ilake@google.com>
Date: Fri May 08 16:10:17 2020
Keep the ordering of ClipData in the resulting list
When combining the Intent's data field and the
Uris in the ClipData, we should attempt to maintain
any ordering present in the ClipData's items.
Test: existing tests pass
BUG: 152941153
Change-Id: I26ee368605054a3e8c090d384ac0843674ee378f
M activity/activity/src/main/java/androidx/activity/result/contract/ActivityResultContracts.java
il...@google.com
Re #4 - As part of Activity 1.2.0-alpha05, we keep the ordering of the ClipData in the final result. There's no guarantee that the ordering there has any relation to the other the user has picked items (or even if it is in first->last or last->first order) since that ordering is completely under the control of the other activity, but it at least serves as a consistent starting point.
We're staying with List for the API side of things; the use of a Set internally is just that - an internal implementation detail.
Description
Version used: 1.2.0-alpha03
Devices/Android versions reproduced on: All
I used the OpenDocuments contract in my project, everything works fine if more than one file is selected in the called explorer.
But if you select only one (which the system does not prohibit) - the contract returns null in response.
I create my own, it seems to me a logical workaround for this situation, but I would like to see this solution out of the box: