Fixed
Status Update
Comments
ar...@gmail.com <ar...@gmail.com> #2
Any updates?
ar...@gmail.com <ar...@gmail.com> #3
updates?
am...@google.com <am...@google.com>
ar...@gmail.com <ar...@gmail.com> #5
any updates on how to do this?
am...@google.com <am...@google.com> #6
Any updates? Are we going to add this in lib?
am...@google.com <am...@google.com> #7
I'm not sure if this is going to be added in the library. In the meantime you can find my implementation here.
https://gist.github.com/fbarthelery/ad0062a88875b46e0065137ff03807a0
ar...@gmail.com <ar...@gmail.com> #8
It would truly be nice if the new tool for fixing navigation (which btw is fantastic) on the platform would support all of the standard top tier UI components. Looking forward to seeing how this goes.
am...@google.com <am...@google.com> #9
Dialog fragments are now used in all modern applications and this is the last missing piece of puzzle to really switch everything to Navigation component.
Hope to see support for this soon enough.
Hope to see support for this soon enough.
co...@gmail.com <co...@gmail.com> #10
Please, any update on this?
ap...@google.com <ap...@google.com> #11
Sometime, there's need to display the previous fragment along with new fragment which is more of like a dialog. Therefore, it will be nice to have this feature in the next update.
ap...@google.com <ap...@google.com> #12
This would be really useful, especially since Modal Bottom Sheets need to be implemented as BottomSheetDialogFragments. It would be great to get all of our navigation into the navigation graph.
ap...@google.com <ap...@google.com> #13
Project: platform/frameworks/support
Branch: androidx-master-dev
commit eec025be7822df951131cc0766b928383f58789e
Author: Ian Lake <ilake@google.com>
Date: Mon Apr 22 14:51:05 2019
Add support for <dialog> destinations
Add support for using a DialogFragment as
a destination in your navigation graph via
the <dialog> tag.
Test: added tests, tested in testapp
BUG: 80267254
Change-Id: I82daaa7bde4efe782095eee7b3932092e9086adb
M navigation/fragment/api/2.1.0-alpha03.txt
M navigation/fragment/api/current.txt
M navigation/fragment/ktx/api/2.1.0-alpha03.txt
M navigation/fragment/ktx/api/current.txt
A navigation/fragment/ktx/src/androidTest/java/androidx/navigation/fragment/DialogFragmentNavigatorDestinationBuilderTest.kt
A navigation/fragment/ktx/src/main/java/androidx/navigation/fragment/DialogFragmentNavigatorDestinationBuilder.kt
A navigation/fragment/src/main/java/androidx/navigation/fragment/DialogFragmentNavigator.java
M navigation/fragment/src/main/java/androidx/navigation/fragment/NavHostFragment.java
M navigation/fragment/src/main/res/values/attrs.xml
A navigation/integration-tests/testapp/src/main/java/androidx/navigation/testapp/LearnMoreDialogFragment.kt
M navigation/integration-tests/testapp/src/main/java/androidx/navigation/testapp/MainFragment.kt
M navigation/integration-tests/testapp/src/main/res/layout/main_fragment.xml
M navigation/integration-tests/testapp/src/main/res/navigation/nav_main.xml
M navigation/integration-tests/testapp/src/main/res/values/strings.xml
https://android-review.googlesource.com/949238
https://goto.google.com/android-sha1/eec025be7822df951131cc0766b928383f58789e
Branch: androidx-master-dev
commit eec025be7822df951131cc0766b928383f58789e
Author: Ian Lake <ilake@google.com>
Date: Mon Apr 22 14:51:05 2019
Add support for <dialog> destinations
Add support for using a DialogFragment as
a destination in your navigation graph via
the <dialog> tag.
Test: added tests, tested in testapp
BUG: 80267254
Change-Id: I82daaa7bde4efe782095eee7b3932092e9086adb
M navigation/fragment/api/2.1.0-alpha03.txt
M navigation/fragment/api/current.txt
M navigation/fragment/ktx/api/2.1.0-alpha03.txt
M navigation/fragment/ktx/api/current.txt
A navigation/fragment/ktx/src/androidTest/java/androidx/navigation/fragment/DialogFragmentNavigatorDestinationBuilderTest.kt
A navigation/fragment/ktx/src/main/java/androidx/navigation/fragment/DialogFragmentNavigatorDestinationBuilder.kt
A navigation/fragment/src/main/java/androidx/navigation/fragment/DialogFragmentNavigator.java
M navigation/fragment/src/main/java/androidx/navigation/fragment/NavHostFragment.java
M navigation/fragment/src/main/res/values/attrs.xml
A navigation/integration-tests/testapp/src/main/java/androidx/navigation/testapp/LearnMoreDialogFragment.kt
M navigation/integration-tests/testapp/src/main/java/androidx/navigation/testapp/MainFragment.kt
M navigation/integration-tests/testapp/src/main/res/layout/main_fragment.xml
M navigation/integration-tests/testapp/src/main/res/navigation/nav_main.xml
M navigation/integration-tests/testapp/src/main/res/values/strings.xml
ap...@google.com <ap...@google.com> #14
We've added support for dialog destinations internally, it'll be available in Navigation 2.1.0-alpha03
Description
I'm doing this the first time, so please have merci ;)
I am using a StaggeredGridLayoutManager in my RecyclerView inside of a Fragment.
While performing a search over a list the vizualisation works as it should and items are getting removed and added.
But after filtering all elements of the list out so the view is empty and then removing the additional letter so the previous items should be seeable again, an ArrayIndexOutOfBoundsException is thrown at java.util.Arrays.checkStartAndEnd(Arrays.java:1732) with the message "start < 0 || end > len. start=-1, end=11, len=11".
I added the output of "adb bugreport" and added also the main folder of my project, so you can hopefully understand what I am talking about and reporoduce the error.
The Exception is happening on all devices I could use to test, inclusive the emulator (I only had Devices with API lvl 22 & 23).
If you need any further informations I will provide them.
Also I hope that this is a real Bug and not caused by my own stupidity.
Yours sincerely,
David Artmann