motion: add smooth exit animation to AppToast and bidirectional slide to WelcomeTourDialog
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 60/100
Research direction
Read lib/shared/widgets/app_toast.dart and lib/features/onboarding/welcome_tour_dialog.dart, tracing toast dismissal and the welcome tour's AnimatedSwitcher navigation. Add a reverse exit animation before onClosed(), animate the remaining toast stack's height changes, and make the slide direction follow forward or back navigation. Done when toast exits and stack repositioning animate smoothly, and backward tour navigation slides in from the opposite direction.
Written by the indexing model from the issue text.
Description
Problem
-
Abrupt toast disappearance:
Inlib/shared/widgets/app_toast.dart, toasts animate their entry with a curved transition, but when the timer expires (_timer = Timer(d.show, _close)), the toast is instantly removed from_ToastHost._items.value. The toast disappears abruptly without a fade/slide-out, causing remaining stacked toasts to jump to their new vertical positions without animation. -
Unidirectional slide in Welcome Tour:
Inlib/features/onboarding/welcome_tour_dialog.dart,AnimatedSwitcheruses a staticSlideTransitionwithbegin: const Offset(0.04, 0). When navigating forward (Next), sliding in from the right looks natural. However, when navigating backward (Back), the incoming step still slides in from the right, which feels unnatural.
Change
- In
AppToast, play_controller.reverse()before triggeringonClosed(), and animate height changes for remaining stacked toasts. - In
WelcomeTourDialog, track navigation direction (forwardvsback) and invert the slide offset sign accordingly.
- Dominant language
- Dart
- Stars
- 23
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 496
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QueryaHub/Querya-Desktop
-
bug P3 ux
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
QueryaHub/Querya-Desktop#1837 ·
Maintainers usually reply within 1 day
-
enhancement P3
Difficulty 4/5 3-5 days Newbie friendliness 50/100
QueryaHub/Querya-Desktop#1838 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
QueryaHub/Querya-Desktop#1690 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 55/100
QueryaHub/Querya-Desktop#1683 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
QueryaHub/Querya-Desktop#1625 · 2 comments ·
Maintainers usually reply within 1 day
All issues in QueryaHub/Querya-Desktop
Similar issues
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
LonelyGriffin/noetec#51 ·
-
Errors after the PostgreSQL server restartsPossibly taken @Fripix claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
TomBursch/kitchenowl#1179 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nucleus-ffm/foss_warn#330 ·
-
needs::triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
linagora/twake-on-matrix#3518 ·
Maintainers usually reply within 3 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
appshubcc/Bettbox#591 · 1 comment ·
Maintainers usually reply within 1 day