makepad-2.0-events

Use either a Splash inline handler with on_click: ||{ ... } directly in script_mod!, or handle it in Rust via handle_actions by calling self.ui.button(cx, ids!(my_button)).clicked(actions). Splash handlers suit UI-level logic; Rust handlers suit business logic and I/O.

Use the script_eval!(cx, { ... }) macro to execute Splash code from Rust, updating mod.state variables and calling ui.view_name.render() to trigger re-renders. Inject Rust values into Splash with the #(expr) interpolation syntax.

on_render is not invoked automatically; you must explicitly call ui.widget_name.render() to trigger it. Also set new_batch: true on the view if you want previous draw content cleared before re-rendering.

Yes. Rust code fires requests with cx.http_request(request_id, req) and receives results in handle_http_response, handle_http_request_error, and handle_http_progress. Splash also supports net.http_request with on_response, on_error, and streaming on_stream callbacks.

Implement handle_key_down in the MatchEvent trait and match on event.key_code with event.modifiers for combinations like Ctrl+S. For widget-level keys, match Hit::KeyDown inside a custom widget's handle_event using event.hits(cx, area).

Dynamically created Splash buttons have unstable UIDs, so the uid_map may not rebuild in time for Rust-side action queries. Always use on_click handlers inside Splash for these buttons instead of relying on handle_actions.