Kitu cha State cha StatefulWidget kina lifecycle — mlolongo wa methods zinazoitwa wakati widget inaundwa, kusasishwa, na kuharibiwa (initState, build, didUpdateWidget, dispose, n.k.). Kuielewa ni muhimu kwa kusimamia rasilimali na side effects kwa usahihi.
class _MyWidgetState extends State<MyWidget> {
@override
void initState() {
super.initState();
// called ONCE when the State is created → initialize, start subscriptions,
// fetch initial data, set up controllers/listeners
}
@override
Widget build(BuildContext context) {
// called whenever the UI needs to render (often) → return the widget tree
return Container();
}
@override
void didUpdateWidget(MyWidget oldWidget) {
super.didUpdateWidget(oldWidget);
// called when the parent rebuilds with new config → react to changed inputs
}
@override
void dispose() {
// called when the State is permanently removed → CLEAN UP:
// cancel subscriptions, dispose controllers, close streams (prevent leaks!)
super.dispose();
}
}
createState → initState (once) → build (many times) → [didUpdateWidget on config change]
→ ... → dispose (once, at the end)
Other: didChangeDependencies (when InheritedWidget dependencies change)
⚠️ dispose() is CRITICAL for cleanup — failing to clean up causes MEMORY LEAKS / bugs:
→ cancel Stream subscriptions, Timers; dispose AnimationControllers, TextEditingControllers,
ScrollControllers; close StreamControllers
→ resources started in initState should be cleaned up in dispose
→ A common source of leaks: forgetting to dispose controllers/subscriptions.
Kuelewa lifecycle ya StatefulWidget ni muhimu kwa kusimamia rasilimali na side effects kwa usahihi katika Flutter, kwa hivyo ni maarifa yenye thamani ya vitendo.
Methods za lifecycle za kitu cha State zinaitwa katika nyakati maalum, na kuzitumia kwa usahihi ni muhimu: initState (inaitwa mara moja wakati State inaundwa — mahali pa kuanzisha, kuleta data ya awali, kuanzisha subscriptions, na kuweka controllers/listeners), build (inaitwa wakati wowote UI inaporender, ikirudisha widget tree), didUpdateWidget (inaitwa wakati parent inajenga upya na usanidi mpya, kwa kuitikia inputs zilizobadilika), na dispose (inaitwa wakati State inaondolewa kabisa).
Kuelewa mtiririko wa kawaida (createState → initState → build mara kwa mara → dispose) hubainisha lini kila moja inaendesha.
Kwa umuhimu mkubwa, kuelewa kwamba dispose ni muhimu kwa cleanup ni maarifa muhimu ya vitendo: kushindwa kusafisha rasilimali (kughairi Stream subscriptions na Timers, ku-dispose AnimationControllers, TextEditingControllers, na ScrollControllers, kufunga StreamControllers) kunasababisha memory leaks na bugs — na kusahau ku-dispose controllers na subscriptions ni chanzo cha kawaida, halisi cha leaks katika programu za Flutter.
Mpangilio wa kuweka rasilimali katika initState na kuzisafisha katika dispose ni wa msingi kwa kuandika widgets sahihi, zisizovuja.
Kuelewa lifecycle kunawezesha initialization ipasavyo (katika initState), kuitikia mabadiliko (katika didUpdateWidget), na kwa umuhimu cleanup (katika dispose).
Kwa kuwa kusimamia rasilimali na side effects kwa usahihi ni muhimu kwa programu sahihi, zisizovuja za Flutter, na kwa kuwa lifecycle ya StatefulWidget (hasa initState kwa kuweka na dispose kwa cleanup) ndiyo utaratibu wa hili, kuelewa lifecycle ya StatefulWidget — methods muhimu, muda wake, na hasa jukumu muhimu la dispose katika kuzuia leaks — ni maarifa muhimu, yanayofaa kivitendo ya Flutter kwa kuandika stateful widgets sahihi, ujuzi muhimu kwa kuepuka resource leaks ambazo ni tatizo la kawaida la Flutter la ulimwengu halisi.