Flutter Mobile Development · Lektion

setState und InheritedWidget

Verstehen Sie die Grundlagen der lokalen Zustandsverwaltung mit `setState` und lernen Sie das Konzept von `InheritedWidget` zur Weitergabe von Daten im Widget-Baum kennen.

setState und InheritedWidget ist eine kostenlose Flutter Mobile Development-Lektion auf CoddyKit. Dies ist Lektion 1 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Flutter Mobile Development-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Flutter Mobile Development-Kurs umfasst insgesamt 4 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

What is State Management?

In Flutter, 'state' refers to any data that can change during the lifetime of a widget. This could be a counter value, user input, or data fetched from the internet.

Managing this changing data, or 'state,' is crucial for building dynamic and interactive mobile applications. We need ways to update the UI when data changes.

Local State with setState

For changes that only affect a single widget, or a small, self-contained part of it, setState is your primary tool. It's used within a StatefulWidget.

Calling setState(() { ... }); tells Flutter that the internal state of this widget has changed and that it needs to rebuild its UI to reflect the new data.

setState in Action: Counter App

Let's build a simple counter. Notice how calling _incrementCounter() updates the _counter variable inside setState, which then triggers the UI to rebuild and show the new count.

import 'package:flutter/material.dart';

class MyCounterApp extends StatefulWidget {
  @override
  _MyCounterAppState createState() => _MyCounterAppState();
}

class _MyCounterAppState extends State<MyCounterApp> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('setState Counter')),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text('You have pushed the button this many times:'),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ),
    );
  }
}

void main() {
  runApp(MaterialApp(home: MyCounterApp()));
}

How setState Triggers Rebuilds

When setState is called, Flutter marks the StatefulWidget as 'dirty' and schedules a rebuild for that widget and its descendants.

Crucially, setState only rebuilds the part of the widget tree rooted at the StatefulWidget where it was called, not the entire application. This helps keep your UI updates efficient.

Limitations: The Problem of Prop Drilling

While setState is great for local state, it becomes cumbersome when you need to share state with widgets deep down the tree.

Passing data through many intermediate widgets that don't actually need it is called 'prop drilling'. It makes code harder to read, maintain, and refactor.

Introducing InheritedWidget

InheritedWidget is a special type of widget designed to efficiently pass data down the widget tree. Any child widget, no matter how deep, can access the data provided by an InheritedWidget.

This solves the 'prop drilling' problem by allowing widgets to 'inherit' data from their ancestors without explicit passing.

Building an InheritedWidget

To create an InheritedWidget, you extend the base class and define the data you want to share. It always requires a child widget, which is the subtree that can access its data.

child: The widget subtree wrapped by this InheritedWidget.
updateShouldNotify: A crucial method that tells Flutter if dependent widgets need to rebuild when the InheritedWidget's data changes.

import 'package:flutter/material.dart';

class MyThemeData extends InheritedWidget {
  final Color primaryColor;

  const MyThemeData({
    Key? key,
    required this.primaryColor,
    required Widget child,
  }) : super(key: key, child: child);

  @override
  bool updateShouldNotify(MyThemeData oldWidget) {
    // Return true if the data has changed, 
    // so dependents rebuild.
    return oldWidget.primaryColor != primaryColor;
  }
}

Accessing InheritedWidget Data

Child widgets retrieve data from an InheritedWidget using a static of(BuildContext context) method. This method efficiently searches up the widget tree for the nearest instance of the specified InheritedWidget.

The context.dependOnInheritedWidgetOfExactType() method is commonly used within the of() method to establish a dependency.

import 'package:flutter/material.dart';

// Assume MyThemeData InheritedWidget is defined elsewhere.
// It needs a static 'of' method:
// static MyThemeData? of(BuildContext context) {
//   return context.dependOnInheritedWidgetOfExactType<MyThemeData>();
// }

class MyColorDisplay extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    // Accessing the InheritedWidget's data using its 'of' method
    final theme = MyThemeData.of(context); 

    return Text(
      'Current color: ${theme?.primaryColor ?? 'Default'}' ,
      style: TextStyle(color: theme?.primaryColor ?? Colors.black),
    );
  }
}

Full InheritedWidget Example

Here's a complete example showing how MyThemeData provides a primary color to a deeply nested MyColorDisplay widget. Notice how MyColorDisplay accesses the data directly via MyThemeData.of(context).

import 'package:flutter/material.dart';

// 1. Our custom InheritedWidget
class MyThemeData extends InheritedWidget {
  final Color primaryColor;

  const MyThemeData({
    Key? key,
    required this.primaryColor,
    required Widget child,
  }) : super(key: key, child: child);

  static MyThemeData? of(BuildContext context) {
    return context.dependOnInheritedWidgetOfExactType<MyThemeData>();
  }

  @override
  bool updateShouldNotify(MyThemeData oldWidget) {
    return oldWidget.primaryColor != primaryColor;
  }
}

// 2. A widget that consumes the data
class MyColorDisplay extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    final theme = MyThemeData.of(context);
    return Container(
      padding: EdgeInsets.all(16.0),
      decoration: BoxDecoration(
        color: theme?.primaryColor ?? Colors.grey,
        borderRadius: BorderRadius.circular(8.0),
      ),
      child: Text(
        'Color Box',
        style: TextStyle(color: Colors.white, fontSize: 18),
      ),
    );
  }
}

// 3. The main app structure
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: Text('InheritedWidget App')),
        body: MyThemeData( // Providing the theme data
          primaryColor: Colors.deepPurple,
          child: Center(
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              children: [
                Text('Data provided by InheritedWidget:'),
                SizedBox(height: 20),
                MyColorDisplay(), // This widget consumes the data
                SizedBox(height: 20),
                Text('This text is also a child.'),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

void main() {
  runApp(MyApp());
}

setState vs. InheritedWidget

When to use which?

setState: Ideal for local, internal state changes within a single StatefulWidget. Simple and direct.
InheritedWidget: Best for sharing data efficiently with multiple widgets deep in the tree, avoiding 'prop drilling'. It's a foundational pattern for more advanced state management solutions.

They solve different problems but are both fundamental to Flutter's state management.

Quick Check: State Management

Consider the following scenarios for managing state in a Flutter application. Which statement accurately describes the primary use case for setState versus InheritedWidget?

Recap: setState & InheritedWidget

Congratulations! You've grasped two core concepts of state management in Flutter:

setState: For managing local, internal state changes within a StatefulWidget.
InheritedWidget: For efficiently sharing data with widgets deep in the tree, avoiding 'prop drilling'.

These foundational patterns are key to building responsive and maintainable Flutter applications. You're now ready to explore more advanced state management solutions!

Häufig gestellte Fragen

Ist die Lektion „setState und InheritedWidget“ kostenlos?

Ja — der vollständige Text von „setState und InheritedWidget“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Flutter Mobile Development-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Flutter Mobile Development-Kurs umfasst insgesamt 4 Lektionen.

Was lerne ich in „setState und InheritedWidget“?

Verstehen Sie die Grundlagen der lokalen Zustandsverwaltung mit `setState` und lernen Sie das Konzept von `InheritedWidget` zur Weitergabe von Daten im Widget-Baum kennen. Du übst Flutter Mobile Development mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um Flutter Mobile Development zu starten?

Keine Vorkenntnisse erforderlich. Flutter Mobile Development auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 1 von 4.

Wie lange dauert die Lektion „setState und InheritedWidget“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser Flutter Mobile Development-Lektion Code schreiben und ausführen?

Ja. Jede Flutter Mobile Development-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

← Zurück zu Flutter Mobile Development