-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example #1
Comments
You can only use NSCL as a direct child of the outer CL, as far as I remember. |
I have the same issue, any workaround when the NSCL is not a direct child of a CL? |
Nope! |
If the nested coordinator layout has to be a direct child of the parent coordinator layout then what is the purpose of it? For example: (Coordinator layout with bottom navigation) -> If I place nested coordinator layout as a direct child it would look like this (Coordinator layout with bottom navigation) -> Would the second setup work? |
In your example, the first one can be a standard Coordinator, the other two should be NSCLs and it will work. If I remember correctly. |
can you give us an example-sample xml file of a complex implementation
what if the only scrollable view of the parent coordinator is inside the child coordinator
RelativeLayout
--CoordinatorLayout
----AppbarLayout
-----LinearLayout(scroll behavior)
-------Framelayout
-------Framelayout
--Framelayout
and add a fragment in the firt Framelayout with
NestedScrollCoordinatorLayout
--AppbarLayout
----Recyclerview(scroll behavior)
The text was updated successfully, but these errors were encountered: