No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

Stopwatch (STOPWATCH)

Measures elapsed time and checks a threshold

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Measures on a stopwatch variable with Start, Stop, Reset and Restart; Elapsed Time (ms) reads the value and Threshold Reached? returns true once the threshold is passed.

When to Use?

Use it to time a section or switch to another flow when a time budget is exceeded.

How to Use?

Pick the Stopwatch Action

Use the same Stopwatch Variable for one measurement (default stopwatch)

Pass the result through the result variable

Parameters

Action

Start, Stop, Reset, Restart, Elapsed Time (ms), Threshold Reached?

Threshold Value

Milliseconds (default 1000)

Result Variable

Elapsed time or threshold result

Parameter	Description
Action	Start, Stop, Reset, Restart, Elapsed Time (ms), Threshold Reached?
Threshold Value	Milliseconds (default 1000)
Result Variable	Elapsed time or threshold result

Example Usage

Start → IMAGE/TEXT scan group → Elapsed Time (ms) → elapsedMs → COMPARE: above 10000 switches to a fallback flow

Combinations / Used With

COMBINATIONS:

STOPWATCH + COMPARE: Time budget decisions

STOPWATCH + BREAK: Leave a loop when the threshold is passed

Tip

Measures elapsed time and checks a threshold

Warnings / Cautions

WARNING:

Resetting before reading loses the measurement

The threshold is in milliseconds (30 seconds = 30000)

Step-by-Step Mastery: Basic → Advanced → Pro

The same block at three levels: a quick start, the real options, and professional techniques.

Basic

STOPWATCH measures how long part of the macro takes. On a Stopwatch variable (default stopwatch) you Action start to begin, then after the steps you want to measure you read elapsed time with elapsed_ms and store it in a Result Variable (default elapsed_ms).

Advanced

Action (stopwatchAction) has six modes: start, stop, reset, restart, elapsed_ms, is_elapsed. start begins, stop halts, reset zeroes, restart zeroes then restarts. elapsed_ms returns the milliseconds elapsed so far. is_elapsed compares against a Threshold (stopwatchThresholdMs, default 1000) and returns true once the time exceeds it — answering "has 15 seconds passed?" in one block. Using the same stopwatch variable consistently keeps the measured span clear.

Pro

Measure performance/SLA at meaningful block boundaries; collecting the whole macro in one stopwatch makes diagnosis impossible — measure each suspect segment (scan, API, OCR) with its own stopwatch variable. is_elapsed is the basis of watchdog-style flows: in a loop check whether you exceeded the budget with is_elapsed and switch to a fallback when you do, giving a controlled exit instead of an infinite wait. The most common mistake is reset/restart before reading and losing the measurement; capture the value into a variable with elapsed_ms first, then reset. Remember timing fluctuates with device load; decide on a trend, not a single reading.

Real-World Scenarios — Step-by-Step Recipes

Small, reproducible examples that combine several blocks — build them straight into your own macro.

Use a fallback if scanning exceeds 10 seconds

1STOPWATCH → Action: start (variable: scanWatch)
2IMAGE/TEXT scan group
3STOPWATCH → Action: elapsed_ms, Result Variable: scanMs
4COMPARE → if scanMs > 10000 switch to fallback flow

Time-budget watchdog in a loop

1STOPWATCH → Action: start (variable: loopWatch)
2Work inside a WHILE loop
3STOPWATCH → Action: is_elapsed, Threshold: 30000
4If it returns TRUE, BREAK out of the loop

Which Blocks to Pair With — Pro Combinations

This block is useful on its own — but it shines when paired with the right partners.

+ COMPARE

Compare the read elapsed_ms against an SLA/timeout threshold to decide.

+ LOG

Log segment durations to keep a performance record.

+ ERROR_HANDLER

Enables a controlled exit and recovery on slowdowns.

+ BREAK

Used to exit a loop when is_elapsed crosses the threshold.

Common Mistakes and Fixes

Doing reset/restart before reading and losing the measurement. Fix: read the value with elapsed_ms first, then reset.

Measuring the whole macro in one stopwatch and failing to find the bottleneck. Fix: measure each segment with its own stopwatch variable.

Treating the is_elapsed threshold as seconds instead of ms and entering a wrong value. Fix: the Threshold is in milliseconds (30 seconds = 30000).

Pro Tips

Use is_elapsed as a watchdog inside loops to turn an infinite wait into a controlled timeout.

Since timing varies with device load, decide on the trend of several runs, not a single measurement.

This Block's Code (Editor View)

Lua

The Lua below is what the Code Editor generates for this block with sample settings. Adding cases, branches, actions or loops, or changing settings, extends the generated code accordingly. Study it to see what the block does under the hood, to learn Lua, or to copy and adapt it. Use the Copy button (top-right) to paste it into the Code Editor, or “Try in Editor →” to run it in the live editor.

lua

Try in Editor →

local sw = nil
local elapsed_val = nil

if sw == nil then sw = Stopwatch() end
elapsed_val = sw:elapsedMs()

Note: generated code can evolve across versions; helper names (e.g. _reg1, m1) and internal optimizations may change. The logic and the called APIs reflect the block’s behavior.

Block ↔ Lua Mapping →

Shared Controls for This Block Family

The guidance below is not identical for every block. It summarizes the professional controls that most often repeat in the selected block family.

🗃Source and Destination

Use file paths, key names, regex sources, and JSON paths with clear naming discipline.

🧷Default Value

Define default outputs clearly so the builder flow does not collapse when data is missing.

🔄Write Then Read Back

For KV or file writes, verifying the result in the next block is healthier in production-grade flows.

🪶Narrow Output Design

Instead of carrying large raw payloads, extract the value you need and pass it forward via a result variable.

Builder vs Lua Boundary

Raw touch pointer lifecycle stays code-first

TOUCH and TOUCH_BREAK cover recipe-style touch flows. Raw pointer choreography such as Touch.down, Touch.move, Touch.up, Touch.dispatch, Touch.reset, Touch.breakAll, and Touch.releaseAfter is not exposed as a first-class builder block.

Touch.downTouch.moveTouch.upTouch.dispatchTouch.resetTouch.breakAllTouch.releaseAfter

Bounded dialog design is builder-backed; freer composition stays code-first

The DIALOG block and dialog designer cover a bounded field set in the builder: Info Text, Text Input, Checkbox, Description, Radio Group, Dropdown, Multi Select, Tab Group, Date Time, Number Range, Slider, Image Picker, Color Picker, File Picker, Recorder Picker, Tag, Signature, and Spacer. The buttons are designed too: the Positive button and Negative button tabs set each button’s text, background, and border color, corner radius, and minimum height next to a preview. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.

Coming soonv1.0.51Two more fields: Agent Detect references (agent_detect_editor) lets the user pick a saved reference set or add and edit references, and Save confirms the selection; Navigation setup editor (navigation_editor) edits a saved map, marker and route from the Dialog and returns the setup and route selection without moving the character.

Setting.builderDialogHudTextViewAgentDetectEditorNavigationEditor

Advanced HTTP request chaining stays code-first

HTTP_GET, HTTP_POST, and HTTP_PUT cover common fixed-method flows; HTTP_REQUEST covers one bounded request with method, header lines, body, content type, query parameters (GET and DELETE), timeout, and a bounded retry. These blocks never throw; they write the status code (-1 on a network failure). Cookie handling, chained request objects, and lower-level client flows still need the code editor.

Request()Request.setCookieRequest.getCookiesCUSTOM_CODE

General programming surfaces stay code-first

The MAP, LIST, JSON_PARSE, REGEX_MATCH, and METRICS blocks cover the everyday cases: map actions, a static list, reading a value from a JSON path, regex match, find, replace, and split, and metrics actions. The rest of the Map, Array, JSON, Regex, and Metrics APIs (for example Array sort, filter, and map) is broader than the builder recipe model and stays on the CUSTOM_CODE and code editor side.

MapArrayJSONRegexMetrics

Low-level runtime and Lua composition stays code-first

Runtime helpers, raw Request objects, Lua built-ins such as print/pcall/xpcall, and free-form object chaining patterns are represented through CUSTOM_CODE or the code editor.

RuntimeRequestprintpcallxpcallCUSTOM_CODE

Debug Mode and Breakpoints

Each block card now exposes an independent breakpoint toggle. When enabled, the breakpoint preference is stored with the block.

Breakpoints are only emitted into runtime code when Debug Mode is enabled from Visual Builder settings. When Debug Mode is off, breakpoints stay saved but do not pause execution.

Use ASSERT for fail-fast validation, and use breakpoints for step-by-step tracing and controlled pauses in the same flow.

Variable Scope

Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.

However, a variable defined inside a GROUP will be 'nil' (undefined) until the GROUP executes. Blocks outside the GROUP using this variable may produce unexpected results.

FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they are outside local scope and should not be used.

TRY_CATCH error variable is only valid within the catch block. If the try block succeeds, the catch branch is not entered and the error variable remains undefined.

TIP: Before using a variable inside a GROUP, assign a default value with SET_VARIABLE outside the GROUP. This way the variable won't be nil even if the GROUP has not run.

Inline Expressions

You can embed variable values and calculations into text fields using {{ expression }} syntax. Expressions inside double curly braces are evaluated as Lua code and the result is inserted into the text.

Syntax

{{ expression }}

Examples

Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1)

{{ name }} kazandı! → tostring(name) .. " kazandı!"

X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)

Supported Blocks

SET_VARIABLELOGCOMPARECLIPBOARD_WRITENOTIFY_TOASTKV_SET

Security Note

Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.

General Tips

Keep scan regions as small as possible — improves speed, reduces false matches.

Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).

Use network operations and error-prone steps inside TRY_CATCH.

If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.

Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.

Customize macros with Dialog block — different parameters each run.

Define repeating steps once with GROUP_CALL, call from many places.

Cross-macro local library

Local Shared Macro Area

The Local Shared Macro Area moves blocks, variables, dialog fields, gallery assets, and imported media dependencies between macros on the same device. It is device-local, not cloud sync, not Firebase sharing, and not a replacement for public macro sharing.

Professional usage model: put a reusable login flow, common scan region, shared dialog form, variable group, template image, color profile, replay recording, or imported PLAY_SOUND media file into the shared area from one macro, then import it from the relevant + menu in another macro.

VISUAL_BLOCKSVARIABLESDIALOG_FIELDSTEMPLATE_IMAGECOLOR_SWATCHREPLAY_RECORDMEDIA_FILE

Send to the shared area

When one item or a multi-selection is active, the shared-area button can copy the selected part from the workspace, group, true/false action branch, dialog, and variables surfaces into the device-local library.

Import into another macro

The shared-area entry under the + menu imports the selected item into the surface that opened it. Main workspace, group, action branch, dialog, and variables each receive the compatible item type.

Share gallery assets

Gallery items include template images, color swatches, replay records, and imported audio/media files. They can move between macros on the same device so repeated templates, colors, recordings, and PLAY_SOUND media assets do not need to be captured again.

Keep it clean

The shared area is not a permanent dumping ground. Delete stale shared items from the shared-library panel; imports create a copy in the target macro and do not rewrite the source macro flow.

Checkpoint: after importing, review block names, linked template/image/color/record/media assets, and variable names in the target macro. The shared area creates a copy; delete stale shared items from the shared-library panel to keep the library clean.

AI assistant

Build a block chain with MH AI in natural language

Tell MH AI what you want in plain language; it proposes the right block sequence and lands it in the workspace after you approve. In the current release it works with cloud providers such as Gemini, Claude, and OpenAI; on-device local models are on the roadmap.

Learn more →