I see mentions of BottomSheetDestinations not bein...
# compose-destinations
b
I see mentions of BottomSheetDestinations not being able to get access to the AnimatedVisibilityScope when using SharedTransitionLayout. Is there any particular reason why that is the case?
r
No reason. But it should work. Where did you see that?
Hi there btw 👋 😁
b
Hello 👋
https://composedestinations.rafaelcosta.xyz/v2/styles-and-animations/ Makes reference to it that it can’t get access to AnimatedVisibilityScope
Also doesn’t like the casting
Copy code
com.ramcosta.composedestinations.bottomsheet.scope.BottomSheetDestinationScopeImpl cannot be cast to androidx.compose.animation.AnimatedVisibilityScope
r
Hmm I need a refresher on this. I’ll let you know here
🙏 1
b
for context, trying to do a shared bounds transition from an element in a LazyColumn in a BottomSheetDestination to a full screen overlay (that scrims the whole window)
r
Im wondering if shared element transitions work across window boundaries. Have you seen such example without compose destinations?
b
they dont work across window boundaries currently tmk 😕
r
So I think that a bottom sheet and an overlay are using their own windows
Right?
If so, maybe that’s why. But again I want to check something on my side too