I'm using the new animations package.
Use case
The user opens the second page, enters information which, after navigating back to the first page, must be available on this first page.
Old way
So far, without the animations package, I just put a 'await' before the Navigator.push() and could call the method, which should be executed when the user navigates back, after that statement.
await Navigator.push(
context,
MaterialPageRoute(builder: (context) => DetailView()),
);
loadData();
Proposal / Question?
How is that possible with the animations package? The Navigator.push() method is called within a void method, so I can't wait for that. I haven't found any other way to do that so far.
I'm using the new animations package.
Use case
The user opens the second page, enters information which, after navigating back to the first page, must be available on this first page.
Old way
So far, without the animations package, I just put a 'await' before the
Navigator.push()and could call the method, which should be executed when the user navigates back, after that statement.Proposal / Question?
How is that possible with the animations package? The
Navigator.push()method is called within a void method, so I can't wait for that. I haven't found any other way to do that so far.