Macro Handler

Macro Handler

Android Automation Platform

Object MethodUI and Dialogs

Setting.get(key, default?)

Returns the value of a saved setting, or default when it is missing. Call it with a dot: Setting:get(...) would pass the Setting table as the key.

Documented for app version 1.0.51Updated:

Detailed Explanation

This section explains when to use the API, how to call it, and which structures it works best with in production flow.

How To Call It

Setting is a global table: call its functions with a dot (Setting.<method>(...)), not a colon.

When To Use It

In dialog and HUD flow, validate user input and complete the sequence with close/dispose steps to keep the UI stable.

Parameters and Return

Required: key. Optional: default (omit to pass nil and use the runtime default). Returns a Lua value of whatever type was stored or read.

Best Combined With

You can combine it with Setting.builder(), Dialog, Checkbox, EditText, Hud, and Console to build richer operator-facing flows.

Example Usage

The snippet below is a starter pattern that can be applied directly in runtime flow.

lua
Try in Editor →
local delay = tonumber(Setting.get("delay", "500")) or 500

Copyable Progressive Examples

From foundation to combined usage, each level is provided as a separate code block so you can copy the level you need and adapt it directly.

Foundation

Shows the shortest direct way to call the API.

Foundation
lua
Try in Editor →
local delay = tonumber(Setting.get("delay", "500")) or 500

Simple

Wraps the base call with minimal flow control.

Simple
lua
Try in Editor →
local stepOk = true
local delay = tonumber(Setting.get("delay", "500")) or 500
if stepOk then
  wait(200)
end

Practical Flow

A practical pattern for real macros with pcall, logging, and guards.

Practical Flow
lua
Try in Editor →
local ok, err = pcall(function()
  local delay = tonumber(Setting.get("delay", "500")) or 500
end)

if not ok then
  print("API step failed: Setting.get: " .. tostring(err))
  requestStop()
end

Detailed

This level packages the API into a reusable helper with error reporting.

Detailed
lua
Try in Editor →
-- In dialog and HUD flow, validate user input and complete the sequence with close/dispose steps to keep the UI stable.
local function run_get_step()
  local delay = tonumber(Setting.get("delay", "500")) or 500
end

local ok, err = pcall(run_get_step)
if not ok then
  toast("Step failed")
  print(err)
end

Combined

Combines the API with related structures to form a more realistic workflow.

Combined
lua
Try in Editor →
local dialog = Setting.builder()
dialog:add("delay", EditText("500", 1, "Delay"))
dialog:add("enabled", Checkbox(true, "Enabled"))
Setting.setDialog(dialog:build())
Setting.show()
local delay = tonumber(Setting.get("delay", "500")) or 500