makepad-2.0-events

What it does

Makes Makepad 2.0's event and action system available to the agent, covering both Splash inline event handlers (on_click, on_render, on_return, on_startup) and Rust-side MatchEvent-based handling (handle_actions, handle_timer, handle_http_response, etc.). It describes how to bridge Splash and Rust via script_eval! and script_apply_eval!, and how to access and manipulate widgets from Rust (button, text_input, slider, etc.).

How it works

• Splashes define inline event handlers in script_mod!, such as on_click and on_render, attached to widgets. These handlers can read and set widget values, trigger re-renders, and call other widget events.
• The Rust layer uses the MatchEvent trait to process business logic and I/O via methods like handle_action, handle_actions, handle_timer, handle_http_response, and more. The Core dispatch requires implementing handle_actions and invoking self.ui.handle_event(cx, event, &mut Scope::empty()) in handle_event to propagate to widgets.
• Communication between Rust and Splash occurs through two macros: script_eval!(cx, { ... }) to execute Splash code from Rust, and script_apply_eval!(cx, widget_ref, { ... }) for targeted runtime property patches.
• Widget access from Rust uses self.ui.widget_type(cx, ids!(name)) and supports various setters and getters for common widgets (Button, TextInput, CheckBox, DropDown, Slider, etc.). Nested IDs and generic access are supported.

When to use it

• Use Splash inline event handlers for UI-level interactions directly in script_mod! when declarative UI logic is preferred (on_click, on_render, on_startup).
• Use Rust MatchEvent for core business logic, I/O, and high-control event handling that require Rust power (handle_actions, handle_http_response, handle_timer, etc.).
• Use script_eval! to update Splash state from Rust and trigger renders; use script_apply_eval! for targeted property patches without running full Splash code.

What it can touch

• Widgets accessed through self.ui: Button, TextInput, CheckBox, DropDown, Slider, RadioButton, LinkLabel, and more.
• It relies on declared tools: claude-code.
• It interacts with Splash via script_eval! and script_apply_eval!, and with the Rust side via the MatchEvent trait implementation.

Caveats

• The review is confined to what the skill explicitly documents: two-layer event system, macros for bridging, and widget access patterns. No speculative outcomes or unstated limitations are provided.
• Implementations require boilerplate like the standard Rust app structure and proper dispatch in handle_event to both MatchEvent and widget UI.