c62bb8b6a1
Currently, if dismiss is called from the content_builder or action_builder, the closing animation doesn't play. This is because the callback happens after the `closing` variable is set, so the animation will only start on the next frame, (and for some reason notify() doesn't trigger another frame?). This change makes it so that the content_builder is called first, so the closing animation starts playing immediately on the same frame. This also adds a check to dismiss to prevent spawning unnecessary futures if it is called multiple times |
||
|---|---|---|
| .. | ||
| locales | ||
| src | ||
| tests/fixtures | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||