Exported Firmware
Generated UI Layer
What 90_Studio_Export.c owns, how it is regenerated and where product logic must not live.
Studio-managed generated code
Generated contents
- —Native LVGL 9 screen and component construction
- —Persisted geometry, styles and themes
- —Private retained objects, state and transition helpers
- —Collision-safe public Runtime SDK implementations for Standard widgets
- —Fi object binding to generated 96_FiRuntime presentation state
- —Genuine-user event adapters
- —Image descriptor declarations and asset registration
- —System Runtime presentation and internal callbacks
- —Generated feature headers, runtime registration and timers
The authoritative Widget Registry decides which semantic capabilities reach this layer. Export-time feature gating keeps unused widget APIs, sources and dependencies out of the generated project.
Representative generated wiring
c
LV_IMAGE_DECLARE(fg_upload_three_position_left);
static fg_three_way_input_t mode = {
.state = FG_THREE_WAY_CENTER,
.changed_cb = FG_On_Mode_Changed,
};
lv_obj_add_event_cb(button, fg_three_way_input_event_cb,
LV_EVENT_CLICKED, &mode);