Why Button class with callbacks in Raspberry Pi? - Purpose & Use Cases

The Big Idea

What if your Raspberry Pi could instantly know when a button is pressed without wasting time checking?

The Scenario

Imagine you want to make a Raspberry Pi project where pressing a button turns on a light or plays a sound. You try to check the button state again and again in your code, watching for when it is pressed.

The Problem

Checking the button manually means your program is stuck constantly asking, "Is the button pressed?" This wastes time and can miss quick presses. It also makes your code messy and hard to change.

The Solution

A Button class with callbacks lets your program wait quietly until the button is pressed, then automatically runs the code you want. This keeps your program clean and responsive without wasting effort.

Before vs After

✗ Before

while True:
    if button_pin.read() == PRESSED:
        do_action()
        break

✓ After

button = Button(pin)
button.when_pressed = do_action

What It Enables

This lets your Raspberry Pi react instantly and cleanly to button presses, making your projects smarter and easier to build.

Real Life Example

Think of a doorbell button: instead of checking all the time if someone pressed it, the system just waits and rings the bell exactly when pressed.

Key Takeaways

Manually checking buttons wastes time and complicates code.

Button class with callbacks waits and reacts automatically.

This makes Raspberry Pi projects more efficient and easier to manage.