You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
From what I could find there is no convenient way that would swap 2 different view! depending on some condition like <Show> with fallback, and yet also have an animation between the transition as <AnimatedShow>.
Describe the solution you'd like
I think its use should look something like this:
This solution works, but I'm sure there are options on how to improve it. The only thing I'm unsure about two things:
fallback, fallback_intro and fallback_outro are optional - whereby in its use it may double <AnimatedShow>
And what about the naming? It's basically a double armed <AnimatedShow>. I'm not sure which way to call it while keeping the name of it's "ancestor"
Describe alternatives you've considered
You could essentially use two <AnimatedShow>s, but it's awkward due to the reason that you have to invert the when of the first + overlapping animations since there's no consistency. And the most baffling thing is that it only accepts MaybeSignal<_> as when, whereas <Show> accepts closure directly with W: Fn() -> bool + 'static.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
From what I could find there is no convenient way that would swap 2 different
view!
depending on some condition like<Show>
withfallback
, and yet also have an animation between the transition as<AnimatedShow>
.Describe the solution you'd like
I think its use should look something like this:
In terms of implementation itself, it is possible to directly take
AnimatedShow
as a basis and just add afallback
as in<Show>
:This solution works, but I'm sure there are options on how to improve it. The only thing I'm unsure about two things:
fallback
,fallback_intro
andfallback_outro
are optional - whereby in its use it may double<AnimatedShow>
<AnimatedShow>
. I'm not sure which way to call it while keeping the name of it's "ancestor"Describe alternatives you've considered
You could essentially use two
<AnimatedShow>
s, but it's awkward due to the reason that you have to invert thewhen
of the first + overlapping animations since there's no consistency. And the most baffling thing is that it only acceptsMaybeSignal<_>
aswhen
, whereas<Show>
accepts closure directly withW: Fn() -> bool + 'static
.The text was updated successfully, but these errors were encountered: