activate method
Called when this object is reinserted into the tree after having been removed via deactivate.
In most cases, after a State object has been deactivated, it is not reinserted into the tree, and its dispose method will be called to signal that it is ready to be garbage collected.
In some cases, however, after a State object has been deactivated, the framework will reinsert it into another part of the tree (e.g., if the subtree containing this State object is grafted from one location in the tree to another due to the use of a GlobalKey). If that happens, the framework will call activate to give the State object a chance to reacquire any resources that it released in deactivate. It will then also call build to give the object a chance to adapt to its new location in the tree. If the framework does reinsert this subtree, it will do so before the end of the animation frame in which the subtree was removed from the tree. For this reason, State objects can defer releasing most resources until the framework calls their dispose method.
The framework does not call this method the first time a State object is inserted into the tree. Instead, the framework calls initState in that situation.
Implementations of this method should start with a call to the inherited
method, as in super.activate().
See also:
- Element.activate, the corresponding method when an element transitions from the "inactive" to the "active" lifecycle state.
Implementation
@override
void activate() {
super.activate();
_updateEffectiveObservers();
for (final NavigatorObserver observer in _effectiveObservers) {
assert(observer.navigator == null);
NavigatorObserver._navigators[observer] = this;
}
}