A State object saka StatefulWidget nduweni siklus hidup — sawijining urut-urutan metode sing dipanggil nalika widget digawe, dianyar, lan dihapus (initState, build, didUpdateWidget, dispose, lsp.). Ngertèni iki penting kanggo ngatur sumber daya lan efek samping kanthi bener.
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.
Ngertèni siklus hidup StatefulWidget penting kanggo ngatur sumber daya lan efek samping kanthi bener ing Flutter, mula iku ilmu praktikal sing barangbaya.
Metode siklus hidup State object dipanggil ing titik-titik tartamtu, lan nggunakake pakaryane kanthi bener iku perlu: initState (dipanggil sapisan nalika State digawe — papan kanggo inisialisasi, njukuk data awal, miwiti langganan, lan nyetup controller/pendengar), build (dipanggil saben kala UI di-render, bali tembung widget), didUpdateWidget (dipanggil nalika induk mbangun ulang karo konfigurasi anyar, kanggo ngarebut owah-owahan input), lan dispose (dipanggil nalika State bola-bali dicopot).
Ngertèni aliran umum (createState → initState → build bola-bali → dispose) ngenerake nalika saben metode dolan.
Paling krusial, ngertèni manawa dispose perlu kanggo pembersihan iku ilmu praktikal penting: gagal ngersèke sumber daya (ngebatali langganan Stream lan Timer, ngbuang AnimationController, TextEditingController, lan ScrollController, nutup StreamController) njalari bocor memori lan kutu — lan lali ngbuang controller lan langganan minangka sumber bocor sing umum lan nyata ing aplikasi Flutter.
Pola nyiapake sumber daya ing initState lan mbersihake ing dispose minangka dhasar kanggo nulis widget sing bener lan tanpa bocor.
Ngertèni siklus hidup ngaktifake inisialisasi bener (ing initState), ngarebut owah-owahan (ing didUpdateWidget), lan paling penting pembersihan (ing dispose).
Samarga ngatur sumber daya lan efek samping kanthi bener iku dadi perlu kanggo aplikasi Flutter sing bener lan tanpa bocor, lan amarga siklus hidup StatefulWidget (utamane initState kanggo nyetup lan dispose kanggo pembersihan) minangka mekanisme kanggo iki, ngertèni siklus hidup StatefulWidget — metode kunci, wektune, lan utamane peran kritis dispose ing cegah bocor — iku ilmu Flutter sing perlu lan praktikal kanggo nulis widget stateful sing bener, katrampilan kunci kanggo ngindhari bocor sumber daya sing dadi masalah nyata ing Flutter.