Limitations

• Pin the Makepad Git revision from Cargo.lock and use that revision’s source/examples for every macro, event and widget method. “2.0” alone is not an API compatibility guarantee; these imported snippets span a changing development branch.
• Do not run bundled scripts without explicit user approval.

When to Use

• Use when building or debugging Makepad UI event routing, widget actions, timer-driven updates, or Rust/Splash communication.
• First identify whether the target uses script_mod/Splash or older live_design APIs; use matching examples.

Makepad 2.0 Event & Action System

Example and verification

For “debounce this search field”, identify the pinned event API, preserve pending input, cancel superseded timers, tag responses to prevent stale updates, and test typing, empty input, cancellation, focus changes and teardown. Repeated Enter/click events must not duplicate a mutation; UI validation is separate from server authorization. Do not log sensitive input or response bodies.

Overview

Makepad 2.0 uses a two-layer event system:

1. Splash Layer -- Inline event handlers written directly in script_mod! Splash code (on_click, on_render, on_return, on_startup). These handle UI interactions declaratively inside the script, close to the widget definitions.