What It Does
TextView(text) performs one focused job in script flow and can be chained cleanly with other API steps. Creates a read-only text label for dialogs.
Creates a read-only text label for dialogs.
This section explains when to use the API, how to call it, and which structures it works best with in production flow.
TextView(text) performs one focused job in script flow and can be chained cleanly with other API steps. Creates a read-only text label for dialogs.
In dialog and HUD flow, validate user input and complete the sequence with close/dispose steps to keep the UI stable. This API becomes most valuable in multi-step chained scenarios.
text define the purpose of the call; preparing them in clearly named variables before execution makes production debugging easier. The safest usage pattern is to store the call result in a variable, wrap it with pcall, and pass it into later steps in a controlled way.
You can combine it with Setting.builder(), Dialog, Checkbox, EditText, Hud, and Console to build richer operator-facing flows.
The snippet below is a starter pattern that can be applied directly in runtime flow.
TextView("Header Text")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.
Shows the shortest direct way to call the API.
TextView("Header Text")Wraps the base call with minimal flow control.
local stepOk = true
TextView("Header Text")
if stepOk then
wait(200)
endA practical pattern for real macros with pcall, logging, and guards.
local ok, result = pcall(function()
TextView("Header Text")
end)
if not ok then
print("API step failed: TextView(text)")
requestStop()
endThis level packages the API into a reusable helper with error reporting.
-- In dialog and HUD flow, validate user input and complete the sequence with close/dispose steps to keep the UI stable.
local function run_textview_step()
TextView("Header Text")
end
local ok, err = pcall(run_textview_step)
if not ok then
toast("Step failed")
print(err)
endCombines the API with related structures to form a more realistic workflow.
local dialog = Setting.builder()
dialog:add("delay", EditText("500", 1, "Delay"))
dialog:add("enabled", Checkbox(true, "Enabled"))
Setting.setDialog(dialog:build())
Setting.show()
TextView("Header Text")