How To Call It
Env is a singleton global table: call its functions with a dot (Env.<method>(...)).
Sets and reads screen cutouts (notches), used to adapt coordinates between the macro and the device.
Documented for app version 1.0.51Updated:
Env is a singleton global table: call its functions with a dot (Env.<method>(...)).
In system flow, design steps as observe first and act second when the API can affect device state.
Env offers 3 methods; each method page lists its parameters and return value.
Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.
The snippet below is a starter pattern that can be applied directly in runtime flow.
Env.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()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.
Env.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()Env.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()
-- Continue with one focused method on the object.Env.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()
local note = "Env overview loaded"
print(note)-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_env_step()
Env.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()
end
local ok, err = pcall(run_env_step)
if not ok then
toast("Step failed")
print(err)
endEnv.setMacroCutouts({ top = 80 })
local cutouts = Env.cutouts()
wait(200)
print("Combined with logging and flow control")