Object MethodSystem Control

System:isScreenOn()

Validates a state on System and returns boolean.

Detailed Explanation

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

What It Does

System:isScreenOn performs one focused job in script flow and can be chained cleanly with other API steps. Validates a state on System and returns boolean.

When To Use It

In system flow, design steps as observe first and act second when the API can affect device state. This API becomes most valuable in multi-step chained scenarios.

Parameters and Return

This entry does not require mandatory parameters. The return type is intended for state validation; drive the flow with if/else or guard patterns.

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

-- System:isScreenOn
local result = System:isScreenOn()
-- Use the result in your script flow

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

-- System:isScreenOn
local result = System:isScreenOn()
-- Use the result in your script flow

Simple

Wraps the base call with minimal flow control.

Simple

lua

local stepOk = true
-- System:isScreenOn
local result = System:isScreenOn()
-- Use the result in your script flow
if stepOk then
  wait(200)
end

Practical Flow

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

Practical Flow

lua

local ok, result = pcall(function()
  -- System:isScreenOn
  local result = System:isScreenOn()
  -- Use the result in your script flow
end)

if not ok then
  print("API step failed: System:isScreenOn")
  requestStop()
end

Detailed

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

Detailed

lua

-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_isscreenon_step()
  -- System:isScreenOn
  local result = System:isScreenOn()
  -- Use the result in your script flow
end

local ok, err = pcall(run_isscreenon_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

-- System:isScreenOn
local result = System:isScreenOn()
-- Use the result in your script flow
wait(200)
print("Combined with logging and flow control")