-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Sticky view at the bottom of bottom sheet #37
Comments
I think it boils down to rendering another composable on top of bottomsheet composable without making it part of bottom sheet itself |
Hey @omkar-tenkale, what's the expected behavior? |
Closer to expected: Tried to achieve expected with this code but the button moves with the sheet, not static at bottom.
|
Hey @omkar-tenkale, sorry for the delayed response. What if you just use |
That actually doesn't fit the use case bit thanks anyway. Looks like it'll be too big of a change for this library |
Actually, you can implement a similar one that seems to be sticky by implementing the content inside the bottom sheet by ordering well the composable functions if you don't really need to create another window, which has the lowest z-order on the view hierarchy. |
correct but the floating view must update its height as well, which needs to coordinate with the sheet scroll listener, but i dont exactly know how, maybe you can share an example? |
Please complete the following information:
Describe the Bug:
Im trying to show a sticky view at bottom of bottom sheet by wrapping the sheet composable and the view within a column but it doesnt seem to work
This causes effect of similar to wrapping the children in a Box composable instead, but the sheet is on top always irrespective of order because it actually adds window on top of views in android.
How can this be implemented correctly? @skydoves
Example:

The text was updated successfully, but these errors were encountered: