makepad-2.0-events: a skill for Makepad 2.0 events

What makepad-2.0-events does

Makepad 2.0 splits event handling across two layers. Inside script_mod! Splash code, handlers sit next to the widgets: on_click, on_render, on_return, on_startup. That covers plain interactivity — a button press, typed text, a redrawn list. The Rust side is the MatchEvent trait, with methods such as handle_actions, handle_timer and handle_http_response. Business logic, network calls and anything needing full Rust belong there.

Two macros connect the layers. script_eval!(cx, { ... }) runs Splash code from Rust, so you can update state and kick off a render. script_apply_eval!(cx, widget_ref, { ... }) patches widget properties at runtime. The skill covers both and says when each fits.

Splash handlers use closure syntax: || for no arguments, |checked| when a value comes in. CheckBox passes its new state, TextInput catches Enter through on_return. on_render does not fire on its own — you call ui.widget_name.render(), and new_batch: true on a view clears the previous draw content first. That last part trips people up.

The Rust section groups the trait methods: lifecycle (handle_startup, handle_shutdown, handle_pause, handle_resume), window focus, frames, widget actions, keys, timers, drawing, HTTP responses and progress, signals, audio devices, MIDI ports, video inputs. By default handle_actions walks every action and calls handle_action for each one.