Closed myounis97 closed 3 months ago
Hello @myounis97, thanks for the bug report. I can confirm this behavior. I will have a look into it 👀
This has been fixed in #130.
You're right that rev
briefly becomes null
. That is if a configuration change like dark mode is not explicitly handled by an application, the Activity
will be restarted. Then RevealState
is restored, since it is saveable, and rev
points to the revealable item again.
However for some reason clickModifier
wasn't properly updated and was still the empty Modifier
from the else
branch. By removing rev != null
from the condition the modifier is properly updated.
The fix will be available in version 3.0.7
.
@myounis97 By the way, what a funny coincidence that your library has a similar name 😁
This has been fixed in #130.
You're right that
rev
briefly becomesnull
. That is if a configuration change like dark mode is not explicitly handled by an application, theActivity
will be restarted. ThenRevealState
is restored, since it is saveable, andrev
points to the revealable item again.However for some reason
clickModifier
wasn't properly updated and was still the emptyModifier
from theelse
branch. By removingrev != null
from the condition the modifier is properly updated.The fix will be available in version
3.0.7
.
Thanks for your efforts 🚀
Describe the bug After switching from/to light/dark mode the overlay view becomes not clickable and the content under the overlay becomes clickable
To Reproduce Steps to reproduce the behavior:
Expected behavior The overlay should intercept click events not the content behind it
Smartphone (please complete the following information):
Additional Context This line becomes null after configuration change
val rev by rememberUpdatedState(currentRevealable.value)
So the launched effect only takes the alpha as key and it would not update the clickModifier