handle2 methods, 3 fields
A capability a descendant app asked for, delivered as the request field on the app_permission_request event payload. Answer it now with :grant() / :deny(), or stash it and answer on a later frame (e.g. when the user picks Allow or Deny). Dropping every reference to it without answering denies the request — promptly when the handler returns without keeping it, but only eventually when a kept reference is released later, so a deferring handler should answer explicitly. A request kept unanswered leaves the requester suspended; it is denied when the keeping app terminates.
datumhue.events.on (in its callback)| Field | Type | Access | Description |
|---|---|---|---|
app | App | read-only | The app that made the request. |
permission | app.Permission | read-only | The requested capability. |
reason | string? | read-only | The justification the requester supplied, or nil when none was given. |
PermissionRequest:grant()Approve the request. The grant is narrowed against the answering app's own holdings — a manager cannot grant a capability it does not itself hold. Raises when the answering app cannot manage the requester, or when the request was already answered; does nothing once the requester has ended.
In the guide: Write a window manager or launcher
PermissionRequest:deny()Refuse the request. Raises when the answering app cannot manage the requester, or when the request was already answered; does nothing once the requester has ended.
In the guide: Write a window manager or launcher