Skip to content

Editable Widgets & DEDs

Many system and config DVs let the wearer change settings directly on the device. They use DEDs (Dedicated Editing Dialogs) — small pop‑up pages that overlay the current screen.

TypeBehaviourExample
bool_inplace / inp_boolToggle a boolean value. Shows localized true/false text.Enable/disable lock in syscfg
1ofN_inplace / inp_1ofnPick one value from a list. Usually auto_ok: true so selection closes the DED immediately.Language selection, log level, LED behaviour
alertsShows a full alert detail skeleton (used only in duress).Tapping an alert in the msglist
inp_1ofn (with title)Same as 1ofN but with a title bar.syscfg language and log level
  • The ded object inside a widget defines the DED type and options.
  • When the user taps the widget, the DED opens.
  • On confirm / auto‑ok, the widget’s onEntry action fires (usually updateLocal or updateOutput), writing the new value to the appropriate devcfg key.
WidgetTypeWrites to
devcfg.ui.lang1ofNdevcfg.ui.lang
devcfg.ui.enable_lockbool_inplacedevcfg.ui.enable_lock
devcfg.ui.log_level1ofNdevcfg.ui.log_level
devcfg.alert.showFlashbool_inplacedevcfg.alert.showFlash
devcfg.alert.showVibrbool_inplacedevcfg.alert.showVibr
devcfg.alert.showSoundbool_inplacedevcfg.alert.showSound
led_colour1ofNdevcfg.led.led0
devcfg.nfc.emulbool_inplacedevcfg.nfc.emul
  • Button actions — how actions like updateOutput are structured
  • syscfg DV — the main config screen using these DEDs