- 24 Nov, 2015 1 commit
-
-
Hixie authored
-
- 22 Nov, 2015 1 commit
-
-
Hixie authored
Now we only use it for things related to ModalRoute and ModalBarrier. (This is easy now that ephemeral routes are gone, so there's no other kind of route to distinguish against.)
-
- 17 Nov, 2015 1 commit
-
-
Hixie authored
This makes HeroController ignore StateRoutes when deciding where to animate heroes to and from.
-
- 16 Nov, 2015 1 commit
-
-
Hixie authored
PageRoute is now MaterialPageRoute. This also changes the following: - Now the HeroController is a Navigator observer, rather than a feature of HeroPageRoutes, which are gone. This means heroes can work between any kind of ModalRoute now. - ModalPageRoute is moved from modal_barrier.dart to routes.dart. - It allows routes to opt-out of their modal barrier being a shortcut to popping the route. - Features of PageRoute that aren't Material-specific get promoted to ModalRoute features: storage, the subtree key, offstageness... The AnimatedModalBarrier is still a ModalRoute feature.
-
- 06 Nov, 2015 1 commit
-
-
Adam Barth authored
We need to use the performance for the "from" route when going backwards. Also, fix a bug in the HeroParty where it would call the quest finished callback multiple times. Fixes #1958
-
- 03 Nov, 2015 1 commit
-
-
Adam Barth authored
Previously, we passed widgets up the hierarchy to display them in the overlay, but that breaks the change propagation logic because those widgets won't get rebuilt. Now we pass WidgetBuilders instead, which can be rebuilt when the overlay rebuilds. Fixes #1913
-
- 31 Oct, 2015 1 commit
-
-
Adam Barth authored
We were trying to do a hero animation from a page to itself, which doesn't make any sense. Now we only render the "to" page offstage if it is different from the "from" page and if its performance isn't already complete.
-
- 30 Oct, 2015 1 commit
-
-
Adam Barth authored
-
- 29 Oct, 2015 1 commit
-
-
Adam Barth authored
In this approach, the hero support is layered on top of the basic navigator functionality.
-