How To Call It
Env is a global table: call its functions with a dot (Env.<method>(...)), not a colon.
Sets the screen cutout insets of the current device, in pixels (the same table form); values set here take the place of the ones read from the display.
Documented for app version 1.0.51Updated:
Env is a global table: call its functions with a dot (Env.<method>(...)), not a colon.
In system flow, design steps as observe first and act second when the API can affect device state.
Required: value. Returns nothing.
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.setDeviceCutouts({ top = 96 })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.setDeviceCutouts({ top = 96 })local stepOk = true
Env.setDeviceCutouts({ top = 96 })
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
Env.setDeviceCutouts({ top = 96 })
end)
if not ok then
print("API step failed: Env.setDeviceCutouts: " .. tostring(err))
requestStop()
end-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_setdevicecutouts_step()
Env.setDeviceCutouts({ top = 96 })
end
local ok, err = pcall(run_setdevicecutouts_step)
if not ok then
toast("Step failed")
print(err)
endEnv.setDeviceCutouts({ top = 96 })
wait(200)
print("Combined with logging and flow control")