Macro Handler

Macro Handler

Android Automation Platform

Object MethodSystem Control

Runtime.setMacroSize(width, height)

Sets the size in pixels of the screen the macro was made on (for example 1080, 2400); coordinates are scaled from it to the current screen. In scripts generated by the no-code editor a 1080 × 1920 call is ignored, because their coordinates are already device pixels.

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

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

When To Use It

In system flow, design steps as observe first and act second when the API can affect device state.

Parameters and Return

Required: width, height. Returns nothing.

Best Combined With

Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.

Example Usage

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

lua
Try in Editor →
Runtime.setMacroSize(1080, 2400)

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 →
Runtime.setMacroSize(1080, 2400)

Simple

Wraps the base call with minimal flow control.

Simple
lua
Try in Editor →
local stepOk = true
Runtime.setMacroSize(1080, 2400)
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()
  Runtime.setMacroSize(1080, 2400)
end)

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

Detailed

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

Detailed
lua
Try in Editor →
-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_setmacrosize_step()
  Runtime.setMacroSize(1080, 2400)
end

local ok, err = pcall(run_setmacrosize_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 →
Runtime.setMacroSize(1080, 2400)
wait(200)
print("Combined with logging and flow control")